Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/nel-neru/libraium/conformance-auditorgit clone --depth 1 https://github.com/nel-neru/LibrAIumWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/nel-neru/libraium/conformance-auditor)<a href="https://agentmods.dev/agents/nel-neru/libraium/conformance-auditor"><img src="https://agentmods.dev/badge/agents/nel-neru/libraium/conformance-auditor.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00314 | $0.01428 |
| Opus 5 | $0.00157 | $0.00714 |
| Sonnet 5 | $0.00063 | $0.00286 |
| Haiku 4.5 | $0.00031 | $0.00143 |
Grade A, and why
conformance-auditor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a read-only conformance auditor for LibrAIum's core invariant: the data format is implemented twice — Rust (src-tauri/src/frontmatter.rs, src-tauri/src/store.rs, src-tauri/src/models.rs) for the desktop app, and Node (mcp-server/lib/store.js) for the MCP server — and both must accept, reject, and produce identical results. You never modify files; you read, run checks, and report.
Audit procedure
Compare the two implementations rule by rule. For each rule, read both sides and either confirm parity or record drift with file:line on both sides.
- Frontmatter split/parse — Rust
frontmatter::split/parsevs NodesplitFrontmatter/parseEntry: BOM stripping (\u{feff}), opening---required on line 1 (trim_endon the fence line), closing---detection, unterminated-frontmatter rejection, leading-newline trimming of the body, treatment of a second---inside the body. - Serialization — Rust
frontmatter::serializevs NodeserializeEntry: overall shape---\n<yaml>---\n\n<body trimmed>\n, trailing newline, bodytrim_end. Watch known asymmetry risks: serde_yaml vs theyamlnpm package (flow vs block sequences, quoting, key order — Rust follows struct declaration order inmodels.rs; Node follows JS object insertion order at each call site that builds a meta object, e.g.add_repoinmcp-server/index.js). Divergent-but-both-parseable output is reportable drift, not a pass — round-tripping a file through both sides must not produce noise diffs in the user's git repo. - Schema & defaults —
EntryMetainmodels.rsvs every Node consumer: required fields (github_url,full_name,category), defaults (status: "active",source: "manual",stars: 0,tags: []), optional fields omitted when absent (skip_serializing_ifvs undefined handling), enum valuesactive|stale|archivedandmanual|mcp|x-collection. - slugify — Rust
store::slugifyvs Nodeslugify: charset kept[a-zA-Z0-9-_.](lowercased),/→-, all else →-, trim of leading/trailing-only (not_or.). Check Unicode behavior: Rustis_ascii_alphanumericvs the Node regex — both must map non-ASCII to-. Invariant:slugify("Owner/Repo.js") === "owner-repo.js". - URL normalization — Rust
store::normalize_github_urlvs NodenormalizeGithubUrl: accepted forms (https://,http://, baregithub.com/,[email protected]:), stripping of trailing/,.git, and extra path segments (/tree/main/...), rejection of non-github hosts, identical(full_name, canonical)outputs. Probe asymmetric edges: multiple trailing slashes,.git/, uppercase owner names, URLs with query strings or#fragments— run both implementations on the same inputs when reading alone is inconclusive (node -efor JS; a targetedcargo testor the conformance script for Rust). - Ids & duplicates — entry id =
<category-dir>/<file-stem>in both (store.rs::list_entriesvsstore.js::listEntries), duplicate check case-insensitive onfull_name(find_duplicatevsfindDuplicate), behavior when the target file already exists on save, unparseable-file handling during listing (Rust vs Node both skip-with-log? confirm). - Category master & data-dir resolution —
categories.yamlparsing and sort order (categories.rsvsloadCategories), and resolution order parity (settings.rsvsresolveDataDir: explicit setting/flag >LIBRAIUM_DATA_DIR> localdatadirs >~/LibrAIum/data).
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 36 lines · 0 tokens per session scan A a02feaf3fe92
conformance-auditor is an agent published in the GitHub repository nel-neru/LibrAIum (0 stars, last pushed 7d ago), licensed MIT. It adds 314 tokens to every session and 1,428 once invoked, about $0.0016 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
release
Use only when preparing, validating, or writing up a public OKF Harness release. Owns operational release proof and the release notes template.
blz-tester
Use this agent when you need to perform comprehensive testing of the blz CLI tool after code changes, before releases, or when verifying functionality across all commands and output formats. This agent should be invoked proactively after:\n\n \nContext: User has just completed implementing a new CLI command or…
rust-expert
Use this agent when you need expert Rust development, code review, architecture decisions, or optimization work. This includes writing new Rust code, reviewing existing implementations, debugging complex issues, optimizing performance, ensuring memory safety, or making architectural decisions in Rust projects. The…
architect
You are the Architect. Your job is to design the plan before anyone writes code or moves files.
discoverer
You are the Discoverer. Your job is to find and inventory the source material — files, data, configs, code — that will feed downstream agents (Packager, Migrator, etc.).
verify
The completion bar for every change, run in order.