agentmods.dev

cadence-completion-auditor

cadence-completion-auditor is an agent for Claude Code from sentasity/cadence. It costs 78 tokens per session (2,305 once invoked), scanned A, original, MIT.

An orchestration agent that checks whether a coding plan was actually implemented. It compares the plan and its linked design with the code changes, then combines findings from several focused checks into one report.

In plain words
What is it for?
Use it after implementation to audit a plan against the codebase, either as part of execution checks or as a report-only review.
Why use it?
A plan can appear complete while important requirements are missing or implemented differently. This agent provides a structured completion check across the whole change.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: model in frontmatter; mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the cadence plugin — 11 skills, 5 agents, 1 hook shipped together

not rated 1repo 13d ago A scan 78 tokens original MIT

Good fit Use it after implementation to audit a plan against the codebase, either as part of execution checks or as a report-only review.

Compare 6 agents from other repositories ↓
View source ↗ sentasity/cadence sentasity.github.io
Install

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.

Claude Code
/plugin marketplace add sentasity/cadence
Claude Code
/plugin install cadence

Made for: Claude Code.

Or install cadence, the plugin that ships this one along with the rest of its 11 skills, 5 agents, 1 hook.

Wrote 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.

agentmods badge for cadence-completion-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/sentasity/cadence/cadence-completion-auditor.svg)](https://agentmods.dev/agents/sentasity/cadence/cadence-completion-auditor)
Your own site
<a href="https://agentmods.dev/agents/sentasity/cadence/cadence-completion-auditor"><img src="https://agentmods.dev/badge/agents/sentasity/cadence/cadence-completion-auditor.svg" alt="Measured on agentmods" height="20"></a>
Per session 78 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,305 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00078 $0.02305
Opus 5 $0.00039 $0.01153
Sonnet 5 $0.00016 $0.00461
Haiku 4.5 $0.00008 $0.00231

Measured 8d ago against content hash 5257a78a3d83, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

cadence-completion-auditor 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 8d 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.

agents/cadence-completion-auditor.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

cadence-completion-auditor

You are the orchestrator behind Cadence's /c-audit skill. You verify a plan was actually implemented against the codebase.

Your contract

Input (from /c-audit skill):

  • The resolved plan handle (per skills/_shared/storage-resolution.md, resolve); the auditor materializes the plan via read_artifact rather than reading a plan folder path.
  • The linked design, resolved from the plan's design-to-plan link per skills/_shared/storage-resolution.md (resolve) and read via read_artifact, not from a raw linked_design: frontmatter line.
  • The resolved config (the JSON printed by node "${CLAUDE_PLUGIN_ROOT}/scripts/resolve-config.js", run from the plan's repo; a .cadence/config.local.yaml overlay participates when present; contract in skills/_shared/config-resolution.md; never read config files directly).
  • The mode: invoked by /c-execute (gating implemented flip) or standalone (report-only).

What you do:

  1. Read the plan overview via skills/_shared/storage-resolution.md (read_artifact) and extract base_sha. If missing, abort with: "base_sha is not set on this plan's overview. /c-execute should have set it on first invocation. Either re-invoke /c-execute or manually set base_sha to the SHA at which execution started."
  2. Compute the diff range: git diff <base_sha>..HEAD.
  3. Read the active audit roster: config.audits.default + config.audits.warnings + config.audits.optional (each with its lethality).
  4. Fan out one sub-agent per audit (via the Task tool). Each sub-agent receives:
    • The audit name (e.g. checkbox-completeness).
    • The audit-specific prompt (from the Audit prompt library section below).
    • The exact slice of plan + diff it needs, taken from the plan the auditor already materialized via skills/_shared/storage-resolution.md (read_artifact) and passed as text (e.g. checkbox-completeness gets the plan's tasks and their checkbox state; build-validator gets the command + working tree). Sub-agents receive plan content as text and never path-read the plan, so they stay backend-blind; audit prompts that say "read the plan folder / phase file" operate on that provided content, and on the notion backend a citation is a slot and step reference rather than a file:line.
    • The expected report shape (pass / fail / warn + citations).
  5. Wait for all sub-agents to return.
  6. Synthesize results into the report shape below.
  7. Return the report.

Read the full file on GitHub · 123 lines

Changes

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.

  1. 8d ago First seen · 123 lines · 78 tokens per session scan A 5257a78a3d83

Subscribe to this mod's changes

cadence-completion-auditor is an agent published in the GitHub repository sentasity/cadence (1 stars, last pushed 13d ago), licensed MIT. It adds 78 tokens to every session and 2,305 once invoked, about $0.0004 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.

Claude CodeCode reviewai-agentsclaude-code-plugindeveloper-toolsworkflow
Related

Other agents, from other repositories

code-reviewer

The pipeline's post-implementation review-and-fix pass — reviews the diff a task's implementation just produced, proves each candidate defect before touching it, fixes the confirmed ones inside the plan's Touches, runs the project's own build and tests, and commits its fixes on top.

SpaiR/task-pipeline · 60 tokens

self-contract-auditor

Read-only auditor for the Contract lens of /self-audit — flags producer↔consumer mismatches in the artifact protocol declared in docs/contract.md, and disagreements between skill templates and the bash parsers (validate.sh, roadmap.sh).

SpaiR/task-pipeline · 54 tokens

self-invariants-auditor

Read-only auditor for the Invariants lens of /self-audit — flags any place where a SKILL.md or bash helper violates an invariant declared in CLAUDE.md § "Invariants — don't break these when editing skills".

SpaiR/task-pipeline · 53 tokens

self-leanness-improver

Read-only improver for the Leanness lens of /self-improve — surfaces prose duplication that should collapse to a single owner plus a pointer, and over-engineering (a bash helper wrapping one line, a dead/unused flag, a phase split that adds ceremony without value). Everything it flags is currently correct and…

SpaiR/task-pipeline · 85 tokens

self-coverage-improver

Read-only improver for the Coverage lens of /self-improve — surfaces missing internal robustness: absent guardrails, missing worked-examples where an agent would guess, unhandled edge-cases in a flow, and missing tests/docs. It proposes rules and safeguards that do not exist yet — distinct from the Invariants auditor…

SpaiR/task-pipeline · 0 tokens

self-docs-sync-auditor

Read-only auditor for the Docs-sync lens of /self-audit — flags drift between README.md, CLAUDE.md, docs/contract.md, and the actual skills/ directory (missing or renamed entries in the pipeline diagram, per-skill summary, comparison tables, skill counts, producer/consumer table).

SpaiR/task-pipeline · 70 tokens