Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add crenshawdev/cadence/plugin install 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/crenshawdev/cadence/cad-minimalism-review)<a href="https://agentmods.dev/skills/crenshawdev/cadence/cad-minimalism-review"><img src="https://agentmods.dev/badge/skills/crenshawdev/cadence/cad-minimalism-review/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/crenshawdev/cadence/cad-minimalism-review"><img src="https://agentmods.dev/badge/skills/crenshawdev/cadence/cad-minimalism-review.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.00036 | $0.00558 |
| Opus 5 | $0.00018 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
cad-minimalism-review 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 11d 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
This pass APPLIES NOTHING. The delete-list is input to the user's decision: no file is edited, deleted, staged or committed, and there is no fix arm to skip. It is a manual, on-demand entry point only - it never auto-fires, and there is no wiring, no gate and no verdict behind it, because a delete-list cannot PASS or FAIL anything.
<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/workflows/minimalism-review.md </execution_context>
-
Run the workflow end-to-end: bracket and dispatch the one
cad-reviewerworker at the session default, then close its bracket the moment the findings are in hand - as a checkpoint when the dispatch came back unusable, which reports NO list rather than an empty one. -
Present the delete-list ranked by
severity, each entry carrying the reviewer's ownfile,line,claimandfailure_scenariounedited; a clean sweep is reported as a result naming the target that was read, never as a bare "no findings". Do NOT delete, edit or apply any of it - the user decides what goes and does it themselves.
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.
- 11d ago First seen · 52 lines · 36 tokens per session scan A 308a6c83a046
cad-minimalism-review is a skill published in the GitHub repository crenshawdev/cadence (5 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 558 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 skills, from other repositories
vibe-review
Use when a PR is open and CI green - dispatches a fresh subagent for two-stage code review (spec compliance then quality), posts findings to the GitHub PR as review comments with severity classification.
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
pr-comment
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…