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 skills add sentasity/cadence --skill c-find-bugsgit clone --depth 1 https://github.com/sentasity/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/skills/sentasity/cadence/c-find-bugs)<a href="https://agentmods.dev/skills/sentasity/cadence/c-find-bugs"><img src="https://agentmods.dev/badge/skills/sentasity/cadence/c-find-bugs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sentasity/cadence/c-find-bugs"><img src="https://agentmods.dev/badge/skills/sentasity/cadence/c-find-bugs.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.01793 |
| Opus 5.5 | $0.00011 | $0.00717 |
| Sonnet 5.5 | $0.00006 | $0.00359 |
| Haiku 4.5 | $0.00003 | $0.00179 |
Grade A, and why
c-find-bugs 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 1mo 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/c-find-bugs
You hunt concrete, fixable defects. Each defect comes with a citation, severity, and a direction for fixing — not a vague "this seems off."
Invocation forms
| Form | Target | Token cost |
|---|---|---|
/c-find-bugs <design-folder> |
Design — logical defects in proposed system | Medium |
/c-find-bugs <plan-folder> |
Plan — execution bugs (missing deps, type mismatches, impossible steps) | Medium |
/c-find-bugs <branch-name> |
Code changes on a branch vs. baseline | Medium |
/c-find-bugs <file-path> |
One file's source | Light |
/c-find-bugs --repo |
Whole repo | Heavy — confirms before starting |
Default scope when no target is given: the current branch's changes since it diverged from main (or config.find_bugs.default_baseline), i.e. git diff <baseline>...HEAD with three dots. A two-dot or bare git diff <baseline> also shows work that landed on the baseline after the branch point, as if the branch had deleted it. If on main itself, ask for explicit target.
Token-cost warning: --repo prints estimated scope (file count, approximate token count) and waits for explicit user confirmation. Other scopes start without confirmation.
What it checks
On code targets (branch / file / repo):
| Category | Examples |
|---|---|
| Correctness | Off-by-one, null-deref, wrong comparison operator, swapped arguments. |
| Logic errors | Conditions that can never be true, dead code paths, infinite loops, missing return statements. |
| Resource handling | Leaked file handles, missing connection close, unclosed transactions. |
| Concurrency | Race conditions, missing locks, double-checked locking bugs. |
| Error handling | Swallowed exceptions, generic except catches, missing error propagation. |
| Security | SQL injection, command injection, hardcoded credentials, missing auth checks. |
| API misuse | Wrong library calls, deprecated APIs, missing required parameters. |
| Time / date | datetime.utcnow() (deprecated), naive datetime comparisons, timezone leaks. |
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.
- 1mo ago Changed · -1 lines · +28 tokens per session 67597bf2e4f3
- 2mo ago First seen · 143 lines · 0 tokens per session scan A f1d23d63897e
c-find-bugs is a skill published in the GitHub repository sentasity/cadence (1 stars, last pushed 22d ago), licensed MIT. It adds 28 tokens to every session and 1,793 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
diagnose
Debugging as the six geniuses at minute scale — the bug confirmed by a red reproduction before any theory, hypotheses plural with kill-reasons before any fix, the fix proven by a fresh green rerun. Use when something is broken, throwing, failing, flaky, or slow, or when the user asks to debug or diagnose.
dw-doctor
Read-only environment diagnostic for a solo-lane repo: whether the tools the hooks and skills assume are installed, and whether the guardrails and the pre-commit really fire here or are silently skipping, each gap reported with a copy-paste fix.
issue
Register a bug, deferral, or known limitation as the next ISS-NNN in docs/registry/ISSUES.md with severity and an investigation path. Use when the user types /genesis:issue, says "log this bug/issue", "defer this", or when work uncovers a problem that will not be fixed in the current task in a GENESIS project.
debugging
Systematic debugging that applies the scientific method to failures. Use when the user says "debug this", "why is this failing", "help me find the bug", or is stuck on a problem and thrashing without progress.
performance
Profiling methodology and optimization strategy for performance work. Use when the user asks to "make this faster", "optimize", "profile", "reduce latency", "fix slow", "improve throughput", or when investigating performance regressions.
sweep
Post-op check for artifacts, damage, and stale references after agent work.