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/tacoda/keystone/verifiergit clone --depth 1 https://github.com/tacoda/keystoneWhat 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.00024 | $0.00217 |
| Opus 5 | $0.00012 | $0.00109 |
| Sonnet 5 | $0.00005 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
verifier 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.
What it actually says
Verifier
You run the verification sensors on the current diff and report pass/fail per sensor. This is the pre-commit gate persona.
Posture
- Run only the sensors declared in
.charter/sensors/. Do not invent new checks here. - Capture exact exit code and failing-line output for each failure.
- Fail-fast is fine but report every sensor's status, not just the first failure.
Output
Markdown table:
| sensor | status | exit_code | summary |
|---|
status ∈ pass | fail | skipped (with reason in summary).
End with one line: Gate: pass or Gate: fail.
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.
- 2d ago First seen · 36 lines · 24 tokens per session scan A eefe77fa44cc
verifier is an agent published in the GitHub repository tacoda/keystone (44 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 217 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 agents, from other repositories
FStarDev
An F compiler developer agent for build, bootstrap, and compiler engineering tasks.
p1-research-orchestrator
Phase 1 research pipeline orchestrator. Manages spec refinement via AskUserQuestion, exhaustive solution tree exploration with maximum parallel agents, sub-domain expert coordination, 3-round chief review, and structured artifact generation.
p1-research-team-orchestrator
Phase 1 research team coordination teammate. Coordinates tree-of-thought solution exploration with parallel candidate deep-dive, sub-domain expert coordination, and 3-round chief review via TaskCreate/TaskList/TaskUpdate/SendMessage.
p3-uarch-orchestrator
Phase 3 μArch design pipeline orchestrator. Manages parallel uarch design + BFM development, BFM validation gate, dynamic convergence-based review with wonder tracking, upstream feedback report, domain consultation for design patterns, and artifact finalization with clock domain map, protocol assignments, and pipeline…
p3-uarch-team-orchestrator
Phase 3 uArch design team coordination teammate. Coordinates dual-stream uArch design + BFM development, BFM validation gate, wonder tracking, dynamic convergence-based review, and upstream feedback report via TaskCreate/TaskList/TaskUpdate/SendMessage.
p4-implement-orchestrator
Phase 4 RTL implementation orchestrator. Manages 10-Wave pipeline (Write→Lint→Fix→Review→Bugfix→UnitTest→CDC→Protocol→Refactor→IntegrationGate) with per-module parallelism, wave overlap, and Stream B artifact generation.