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.
git clone --depth 1 https://github.com/selectess/fde-consultants-protocolesWrote 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/selectess/fde-consultants-protocoles/fde-certify)<a href="https://agentmods.dev/commands/selectess/fde-consultants-protocoles/fde-certify"><img src="https://agentmods.dev/badge/commands/selectess/fde-consultants-protocoles/fde-certify.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.00012 | $0.00069 |
| Opus 5 | $0.00006 | $0.00034 |
| Sonnet 5 | $0.00002 | $0.00014 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
fde-certify 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 7d 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
Run python3 -m modex.certify_skill --skill-path ./skill --output ./cert.json and explain the resulting FDE Assurance Score component by component (claim / contradiction / evidence / anti-patterns), including what would raise the weakest component.
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.
- 7d ago First seen · 5 lines · 12 tokens per session scan A 5fdf082ae04d
fde-certify is a command published in the GitHub repository selectess/fde-consultants-protocoles (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 69 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-31.
Other commands, from other repositories
traceability
Generate requirements traceability matrix from requirements to design to tests.
replay
Replay recorded AI traces to detect behavioral drift between model versions.
feature
Start a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline. The one entry to implementation.
fix
Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.
ai-act-scan-fix
Scan a codebase, then propose concrete remediation (code edits, new files, tests) for the top compliance gaps. Does NOT auto-apply — always shows the plan first.
metago-verify
A command that runs a structured verification process across code, network links, API responses, rendering, interactions, saved state, security boundaries, and possible defects.