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 commands/tobiasosborne/alethfeld/validate-graphgit clone --depth 1 https://github.com/tobiasosborne/alethfeldWrote 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/commands/tobiasosborne/alethfeld/validate-graph)<a href="https://agentmods.dev/commands/tobiasosborne/alethfeld/validate-graph"><img src="https://agentmods.dev/badge/commands/tobiasosborne/alethfeld/validate-graph.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.1 | $0.00013 | $0.00697 |
| Opus 5 | $0.00006 | $0.00349 |
| Sonnet 5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
validate-graph 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 5d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Proof Graph Validator
Validate EDN proof graph files against the Alethfeld protocol schema and semantic invariants.
Input
The user will provide a file path to an EDN proof graph (.edn). If no path is provided, prompt for one or search for .edn files in the current directory.
Validation Protocol
1. Run the Validator
./cli/scripts/alethfeld validate -v <path-to-edn-file>
The -v (verbose) flag provides detailed error information.
2. Interpret Results
Exit codes:
0- Validation successful (all checks pass)1- Validation failed (schema or semantic errors)2- File error (not found, parse error, etc.)
3. Validation Checks Performed
Schema Validation (Malli):
- Node structure:
:id,:type,:statement,:content-hash,:dependencies,:scope,:justification,:status,:taint,:depth,:parent,:display-order,:provenance - Valid node types:
:assumption,:local-assume,:local-discharge,:definition,:claim,:lemma-ref,:external-ref,:qed - Valid justifications: 23 allowed keywords (
:modus-ponens,:universal-intro, etc.) - Valid statuses:
:proposed,:verified,:admitted,:rejected - Valid taint values:
:clean,:tainted,:self-admitted - Symbol, external-ref, lemma, and metadata structure
Semantic Validation:
- Referential integrity: All
:dependenciesreference existing nodes; all:lemma-idand:external-idreferences exist - Acyclicity: No cycles in the dependency graph
- Scope validity:
:scopeentries are valid (undischarged ancestor:local-assumenodes) - Taint correctness:
:taintvalues match computed values based on:statusand dependencies
Output Format
On success:
OK: All validations passed
On failure, report:
VALIDATION FAILED: <filename>
================================
ERRORS:
- [<error-type>] <detailed message>
- ...
SUMMARY:
- Schema errors: <n>
- Semantic errors: <n>
RECOMMENDATIONS:
- <specific fixes for each error>
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.
- 5d ago First seen · 89 lines · 13 tokens per session scan A bdf8af917f38
validate-graph is a command published in the GitHub repository tobiasosborne/alethfeld (144 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 697 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.