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 hxt9805/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/commands/hxt9805/cadence/cadence-init)<a href="https://agentmods.dev/commands/hxt9805/cadence/cadence-init"><img src="https://agentmods.dev/badge/commands/hxt9805/cadence/cadence-init.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.00017 | $0.00051 |
| Opus 5 | $0.00009 | $0.00026 |
| Sonnet 5 | $0.00003 | $0.00010 |
| Haiku 4.5 | $0.00002 | $0.00005 |
Grade A, and why
cadence-init 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.
What it actually says
请按照 ${CLAUDE_PLUGIN_ROOT}/skills/cadence-init/SKILL.md 的主流程，在当前项目初始化 cadence 工作流。
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 · 6 lines · 17 tokens per session scan A 6d0f4080d789
cadence-init is a command published in the GitHub repository hxt9805/cadence (5 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 51 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
interview
Interview & refine a spec, task, or spec file in-depth.
capture
Synthesize the current conversation into a flow-next spec at .flow/specs/ .md — source-tagged, mandatory read-back, no silent overwrite.
tracker-sync
Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync).
audit
Audit .flow/memory/ entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry.
chart
Decision-map discovery for one oversized/unclear idea before capture - ground, chart a frontier, resolve one decision per invocation, brief for capture.
features
Seed or maintain the committed user-POV feature map at .flow/features/.