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/blekline/blekline-oss/verify-governancegit clone --depth 1 https://github.com/Blekline/blekline-ossWrote 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/blekline/blekline-oss/verify-governance)<a href="https://agentmods.dev/commands/blekline/blekline-oss/verify-governance"><img src="https://agentmods.dev/badge/commands/blekline/blekline-oss/verify-governance.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.00018 | $0.00091 |
| Opus 5 | $0.00009 | $0.00046 |
| Sonnet 5 | $0.00004 | $0.00018 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade B, and why
verify-governance scanned grade B with 1 finding 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
2. `.mcp.json` / `.blekline/policy.json` tokens are `blw_...` placeholders unless the user configured a live token locally. The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 9 lines · 18 tokens per session scan B 4a8ab31950cf
verify-governance is a command published in the GitHub repository Blekline/blekline-oss (1 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 18 tokens to every session and 91 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
add-memory
Add a new memory to the current project.
model-audit
Audit model usage across the team to identify cost optimization opportunities.
usage-report
Generate a comprehensive team usage and spending report for the current billing cycle.
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.