npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@agentrel/core

v0.1.0

Published

AgentRel core — pure-function parsers, drift analyzer, and score calculator for AI tooling configuration files.

Readme

@agentrel/core

Pure-function parsers, drift analyzer, and synthesizer for AgentRel. This is the L1 logic library — no node:fs, no node:http, no node:https, no analytics SDKs. Safe to use from Node, Bun, Cloudflare Workers, or any other JavaScript runtime that ships ES modules.

If you're a CLI user, install agentrel instead. This package is for embedding the drift detector into your own tooling.

Install

npm install @agentrel/core

Quick start

import { analyzeDrift, parseMarkdown, renderScanJson } from '@agentrel/core'

const agents = parseMarkdown('AGENTS.md', agentsMdContent)
const claude = parseMarkdown('CLAUDE.md', claudeMdContent)

const conflicts = analyzeDrift(agents, claude)
const json = renderScanJson({ conflicts }, ['AGENTS.md', 'CLAUDE.md'])

The library is platform-agnostic: you supply file contents as strings (no IO). Two seams let you wire IO from your runtime:

  • FileSourcelist() + read(path) for ingesting target files
  • FileTargetwrite(path, content) for writing synthesized output

Node implementations live in the agentrel CLI package as NodeFileSource and NodeFileTarget. Edge / worker implementations are yours to write.

Public API

// Drift detection
export function analyzeDrift(a: ParsedConfig, b: ParsedConfig): Conflict[]
export function parseMarkdown(path: string, content: string): ParsedConfig

// Bootstrap
export function init(source: FileSource, target: FileTarget, opts?: InitOptions): Promise<InitResult>
export function synthesize(signals: InitSignals): SynthesizedFiles

// Rendering
export function renderScanJson(result: ScanResult, filesScanned: readonly string[]): string
// (HumanRenderer lives in the `agentrel` CLI package — needs picocolors.)

// Errors — all extend AgentrelError, all carry what / why / nextStep
export class AgentrelError extends Error { readonly exitCode: 1 | 2 }
export class ParseError extends AgentrelError {}
export class IOError extends AgentrelError {}
export class ConfigError extends AgentrelError {}
export class AlreadyExistsError extends AgentrelError {} // exit 1
export class NoIdeDetectedError extends AgentrelError {} // exit 1

Types: Conflict, ConflictKind, ConflictLocation, FileSource, FileTarget, ParsedConfig, ParsedSection, FencedBlock, ScanResult, ScanJsonReport, InitResult, InitOptions, InitSignals, SynthesizedFiles, Severity, Renderer.

Constants: SEVERITY_WEIGHTS, MIN_SCORE, MAX_SCORE, DRIFT_HEADER, NO_DRIFT_MESSAGE, NO_CONFIG_FILES_MESSAGE, CLAUDE_SKILL_DATA_POLICY_DISCLOSURE.

What's a "conflict"?

Two detection paths run per scan:

  • Command drift — for each intent heading (Build / Test / Dev / Install) present in both files, compare the first fenced code block. Different commands emit a command conflict.
  • Forbidden-behavior drift — prescriptive prose statements ("always X", "never Y") in matching topic clusters that disagree emit a forbidden-behavior conflict.

One-sided absence (a section in only one file) is not drift.

Trust posture

The published package has no fetch / http / https imports, no analytics SDKs, no postinstall script. The only runtime dependency is gray-matter for YAML frontmatter parsing. Trust-posture-as-code lint enforcement (NFR7) lands in v0.2.

License

Apache-2.0