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 sentasity/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/sentasity/cadence/c-audit)<a href="https://agentmods.dev/skills/sentasity/cadence/c-audit"><img src="https://agentmods.dev/badge/skills/sentasity/cadence/c-audit.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.00104 | $0.02119 |
| Opus 5 | $0.00052 | $0.01059 |
| Sonnet 5 | $0.00021 | $0.00424 |
| Haiku 4.5 | $0.00010 | $0.00212 |
Grade A, and why
c-audit 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 7d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/c-audit
You verify a plan was actually implemented. You delegate the heavy lifting to the cadence-completion-auditor agent (which orchestrates per-audit sub-agents); your job is pre-flight, invocation, and surfacing the agent's report to the user.
Architecture: standalone wrapper around the auditor agent
This skill is the standalone invocation path. /c-execute does NOT route its completion-gate audit through this skill — it dispatches cadence-completion-auditor directly. The agent is the single source of truth for audit logic; both invocation paths (this skill, and /c-execute's gating call) dispatch the same agent with the same parameters and produce identical results.
This means: if you ever change audit behavior, change the agent. Changing this skill only affects the standalone UX (pre-flight messages, output formatting).
Invocation form
/c-audit <plan-path> — standalone. Report only; do NOT flip status. There is no "called internally by /c-execute" mode — /c-execute doesn't call this skill, it dispatches the agent directly.
Pre-flight (in order)
- Plan artifact exists — resolve the plan slug via
skills/_shared/storage-resolution.md(resolve); it must have an00-overview. - Linked design exists. Read the plan overview via
skills/_shared/storage-resolution.md(read_artifact), then resolve the linked design (resolve) and confirm it exists withstatus: approvedor later — do not read a rawlinked_design:frontmatter line or assume a design folder path. base_sha:is set. Read it from the plan overview viaskills/_shared/storage-resolution.md(read_artifact). If missing:- Abort with: "
base_shais not set on this plan's overview. /c-execute should have set it on first invocation. Either re-invoke /c-execute (which recordsbase_sha) or manually setbase_shato the SHA at which execution started."
- Abort with: "
- Diff range computable.
git diff <base_sha>..HEADshould not error. If it does (e.g.base_shanot in current branch's history), surface the git error verbatim.
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.
- 7d ago First seen · 113 lines · 104 tokens per session scan A efac4c6693c2
c-audit is a skill published in the GitHub repository sentasity/cadence (1 stars, last pushed 12d ago), licensed MIT. It adds 104 tokens to every session and 2,119 once invoked, about $0.0005 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
self-audit
Self-audit this skills repo against CLAUDE.md invariants, the artifact contract, and README/CLAUDE.md/docs sync via three parallel read-only subagents. Local meta-skill — independent of the /task: pipeline.
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…
code-review
The depth half of a review - the dimensions a diff is read against (correctness, boundaries, concurrency, failure paths, secrets, data access, structure, test quality) and the rule that a finding is refuted before it is reported. The verdict stays with the reviewer agent. Use when reviewing a diff or a pull request…
deslop
The optimization pass, defined - delete before you add, one smell class per pass, behaviour pinned by a test that ran BEFORE the edit. Lints a SKILL.md and prose by the same instinct. Use for the per-story optimization pass or when code has grown noisy without growing capable.
loop-test
A local experiment for designing repeating checks with Claude Code’s loop command. It covers both fixed intervals and checks that schedule themselves again after each run.
take-task
A workflow for claiming a tracker task and preparing the development branch for it. It verifies the task, marks it as in progress, checks for uncommitted changes, and handles branch setup according to the task state.