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/crenshawdev/cadenceWrote 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/agents/crenshawdev/cadence/cad-plan-checker-xhigh)<a href="https://agentmods.dev/agents/crenshawdev/cadence/cad-plan-checker-xhigh"><img src="https://agentmods.dev/badge/agents/crenshawdev/cadence/cad-plan-checker-xhigh.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.00034 | $0.00135 |
| Opus 5 | $0.00017 | $0.00068 |
| Sonnet 5 | $0.00007 | $0.00027 |
| Haiku 4.5 | $0.00003 | $0.00014 |
Grade A, and why
cad-plan-checker-xhigh 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 yesterday.
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
Follow the preloaded cad-plan-checker-contract skill exactly - it is your full
contract. This file names that contract and adds nothing else.
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.
- yesterday Changed fb3b965baede
- 7d ago First seen · 15 lines · 34 tokens per session scan A 74c25e288e0c
cad-plan-checker-xhigh is an agent published in the GitHub repository crenshawdev/cadence (4 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 135 once invoked, about $0.0002 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 agents, from other repositories
gitops
Git operations specialist. MUST BE USED for branch management, conflict resolution, git history analysis, worktree recovery, commit, merge, push. Owns ALL git operations — other agents do NOT commit.
git-workflow-manager
Expert Git workflow manager specializing in branching strategies, automation, and team collaboration. Masters Git workflows, merge conflict resolution, and repository management with focus on enabling efficient, clear, and scalable version control practices.
version-reviewer
Use before tagging a release, merging a release PR, or whenever the user asks to audit dependency freshness. Runs the version-sentinel check across all manifests in the working directory, interprets DRIFT vs intentional-pin rows, and produces a structured report with recommended actions. Read-only — does not edit…
deployment-engineer
Configure and optimize deployment pipelines, container packaging, and release automation. Ensures resilient rollouts, observability, and compliance across environments. Engage when establishing or upgrading delivery infrastructure.
pr-standards
Git Commit & PR Standards for AI-Assisted Development.
implementer
Implements ONE planned item in the isolated worktree, exactly one commit per item. Use after planner + navigator, and again on each gate/review loopback to fix only the reported findings.