Specs.consistency-check

A cross-project consistency check for the current branch. It compares the ADRs, schema package, command-line interface, and website documentation to find mismatches before merging.

In plain words
What is it for?
Use it before a merge to find missing or conflicting updates across adr/, packages/schema/, packages/cli/, and site/.
Why use it?
It catches cases where the recorded decision, code, CLI behavior, and documentation describe different things.

Agent

Install

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.

agentmods
npx agentmods add agents/directededges/specs/specs.consistency-check
Clone the repo
git clone --depth 1 https://github.com/DirectedEdges/specs
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,292 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.01292
Opus 5 $0.00011 $0.00646
Sonnet 5 $0.00004 $0.00258
Haiku 4.5 $0.00002 $0.00129

Measured 2d ago against content hash d3e8a5bfe099, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Specs.consistency-check 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 2d 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.

.github/agents/Specs.consistency-check.agent.md · 119 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 119 lines · 22 tokens per session scan A d3e8a5bfe099

Subscribe to this mod's changes

Specs.consistency-check is an agent published in the GitHub repository DirectedEdges/specs (125 stars, last pushed 4d ago), with no licence file. It adds 22 tokens to every session and 1,292 once invoked, about $0.0001 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-30.