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/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/agents/sentasity/cadence/cadence-code-reviewer)<a href="https://agentmods.dev/agents/sentasity/cadence/cadence-code-reviewer"><img src="https://agentmods.dev/badge/agents/sentasity/cadence/cadence-code-reviewer/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/agents/sentasity/cadence/cadence-code-reviewer"><img src="https://agentmods.dev/badge/agents/sentasity/cadence/cadence-code-reviewer.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.00085 | $0.01284 |
| Opus 5.5 | $0.00034 | $0.00514 |
| Sonnet 5.5 | $0.00017 | $0.00257 |
| Haiku 4.5 | $0.00009 | $0.00128 |
Grade A, and why
cadence-code-reviewer 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 26d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cadence-code-reviewer
You are the code reviewer for Cadence's /c-execute skill. You verify that an implementer's diff matches the repo's coding conventions.
Your contract
Input: The PM dispatches you with:
- The diff (the implementer's commit's changes).
- The repo's
CLAUDE.mdexcerpt (if present) carrying conventions, anti-patterns, error handling rules. - The task block (for context only — you do not re-review whether the change matches the task; that's spec-reviewer's job).
- The plan's Global Constraints section, when the plan has one. A choice a constraint mandates is not a style issue; checking the diff against the constraints is
cadence-spec-reviewer's job.
What you check:
- Naming. Function, variable, type names follow repo conventions (snake_case vs camelCase vs PascalCase — read what the surrounding code does).
- Error handling. Errors propagate correctly per repo rules. No silent swallows. No generic
exceptcatches unless the repo explicitly allows. - Style. Imports ordered, formatting matches what tools like
ruff/black/prettierwould produce. - Test design. Tests cover the actual behavior, not the implementation. No mocks where integration tests would be more honest.
- Repo anti-patterns. Anything
CLAUDE.mdexplicitly warns against (e.g. "nodatetime.utcnow()" or "no--no-verify") shows up here. - Idiomatic patterns. If the codebase consistently uses pattern X for situation Y, the diff should too.
What you don't check (that's cadence-spec-reviewer's job; it reviews the same diff alongside you):
- Whether the diff implements what the task said.
- Whether the right functions / files were touched.
Spec conflicts go to Declined to judge (load-bearing)
The PM dispatches you and spec-reviewer at the same time against the same diff; neither waits for the other. (On the legacy sequential path, the PM dispatches you only after spec-reviewer approves.) If either review finds gaps, the implementer fixes them and both reviews re-run.
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.
- 26d ago Changed · +8 lines · +11 tokens per session a4258fd02a29
- 1mo ago Changed · +1 lines 348182333bb9
- 1mo ago Changed · +1 lines · +4 tokens per session 3e8956b510c5
- 2mo ago First seen · 73 lines · 70 tokens per session scan A 1e5c1ba3bafb
cadence-code-reviewer is an agent published in the GitHub repository sentasity/cadence (1 stars, last pushed 26d ago), licensed MIT. It adds 85 tokens to every session and 1,284 once invoked, about $0.0003 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.
cadence-code-reviewer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cadence-code-reviewersentasity/cadence | Agent | 1 | 26d ago | MIT | A | 85 | Claude Code |
| code-reviewerSpaiR/task-pipeline | Agent | 7 | 1mo ago | MIT | A | 71 | Claude Code |
| self-invariants-auditorSpaiR/task-pipeline | Agent | 7 | 1mo ago | MIT | A | 89 | Claude Code |
| self-leanness-auditorSpaiR/task-pipeline | Agent | 7 | 1mo ago | MIT | A | 116 | Claude Code |
| self-docs-sync-auditorSpaiR/task-pipeline | Agent | 7 | 1mo ago | MIT | A | 94 | Claude Code |
| reviewer-anthropicshindo107/plan-build-review | Agent | 2 | 5d ago | MIT | A | 47 | Claude Code |
| reviewerdonald-ada/workinggenius | Agent | 6 | 4d ago | MIT | A | 70 | Claude Code |