Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/hxt9805/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/plugins/hxt9805/cadence/marketplace)<a href="https://agentmods.dev/plugins/hxt9805/cadence/marketplace"><img src="https://agentmods.dev/badge/plugins/hxt9805/cadence/marketplace/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/plugins/hxt9805/cadence/marketplace"><img src="https://agentmods.dev/badge/plugins/hxt9805/cadence/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cadence marketplace 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 1mo 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
{
"name": "cadence",
"description": "Marketplace for cadence workflow plugin",
"owner": {
"name": "hxt9805"
},
"plugins": [
{
"name": "cadence",
"description": "讨论驱动的通用项目工作流插件(Claude Code 与 OpenCode 均 first-class,Codex 兼容层)。",
"version": "0.6.1",
"source": {
"source": "url",
"url": "https://github.com/hxt9805/cadence.git",
"ref": "v0.6.1"
}
},
{
"name": "cadence-preview",
"description": "预览版(preview 分支 — 新功能,可能不稳定)。Stable 装 cadence@cadence。",
"source": {
"source": "url",
"url": "https://github.com/hxt9805/cadence.git",
"ref": "preview"
}
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 29 lines scan A c7cb92508f04
cadence marketplace is a plugin published in the GitHub repository hxt9805/cadence (5 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
flow-next
Zero-dependency, spec-driven agentic SDLC: durable specs, context-fit plans, re-anchored workers, adversarial cross-model review, and receipts. Includes 21 subagents, 26 commands, 29 skills.
ticket-flow
Beads-backed ticket workflow for Claude Code: spec → pickup → implement → finish behind verdict and merge gates, orchestrated by /flow (--local with resume, --parallel, --serial/--loop unattended queue runner), each ticket in its own git worktree. Five visible commands; the phase skills are model-invoked.
smithy
A Claude Code workflow plugin for durable task state: anvil orchestration, forge planning, quench clarification, and polish review.
autoworker
Auto-loop execution workflow with quality gates for Claude Code. Automatically decomposes tasks, implements code, runs tests, and iterates through quality gates until completion.
qiushi-skill
Qiushi Skill: methodology skills for AI agents guided by seeking truth from facts.
periagoge
Name what your cases share, say which cases it takes in and leaves out, and recognize it as serving your goal — /induce (περιαγωγή: turning-around).