Borrowing it
Nothing to install: this file belongs to thomas-powers-jr/cadence. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/thomas-powers-jr/cadence/main/.claude/commands/cadence-scout.mdgit clone --depth 1 https://github.com/thomas-powers-jr/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/commands/thomas-powers-jr/cadence/cadence-scout)<a href="https://agentmods.dev/commands/thomas-powers-jr/cadence/cadence-scout"><img src="https://agentmods.dev/badge/commands/thomas-powers-jr/cadence/cadence-scout/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/commands/thomas-powers-jr/cadence/cadence-scout"><img src="https://agentmods.dev/badge/commands/thomas-powers-jr/cadence/cadence-scout.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.00016 | $0.00435 |
| Opus 5 | $0.00008 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
cadence-scout 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
!cadence recommend
You are running CADENCE scout — a divergent→convergent ideation dialogue that turns a fuzzy problem into ranked Praxis recommendations. Scout never drives the loop: it generates candidate directions and lands them in the recommendation ledger. It allocates no loop id, runs no gate, and never changes loop state.
Topic: $ARGUMENTS — if empty, ask the user what space to scout.
The ranked recommendations above (!cadence recommend) are your
orientation: don't re-propose work already captured or in flight.
Before landing anything, mint one scout-session id for this run in the
form scout-YYYYMMDD-HHMM (use the current date + time). Pass it as
--scout-id on every rec you land so the whole session is queryable as a
cluster later via cadence recommend --scout-id <id>.
- Diverge. Generate many candidate directions for the topic — breadth first, no commitment, no filtering yet. Aim wide.
- Converge. Triage with the user down to the few worth keeping; drop duplicates of existing recs and merge near-duplicates.
- Land. For each survivor run:
cadence recommendation add --title "<title>" --readiness raw-idea --scout-id <scout-YYYYMMDD-HHMM> --evidence "Generated in /cadence-scout session on <topic>, <date>; siblings: <other rec ids>"— use--readiness needs-evidencewhen the candidate is already well-formed. - Hand back. Point the user at
cadence recommendto re-rank, then the existing rec → milestone → SPEC export path. Scout stops here.
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 · 39 lines · 16 tokens per session scan A b4123289198e
cadence-scout is a command published in the GitHub repository thomas-powers-jr/cadence (2 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 435 once invoked, about $0.0001 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 commands, from other repositories
init
Initialize the current repository for herdrpowers by declaring repo-specific configuration in its instruction files.
poly-check
Lint and check formatting with poly — apply no fixes; summarize findings and drift.
poly-fix
Apply poly lint --fix and fmt --fix, then re-check and report what changed and what remains.
execute_parallel
Interactive workflow for isolated parallel execution across herdr panes, testing, review, and cleanup.
full_cycle
Interactive workflow to execute the entire development cycle from brainstorming to the integration decision.
execute
Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.