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.
/plugin marketplace add crenshawdev/cadencenpx agentmods add plugins/crenshawdev/cadence/cadencegit clone --depth 1 https://github.com/crenshawdev/cadenceGrade A, and why
cadence 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 yesterday.
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",
"displayName": "Cadence",
"description": "A plan/execute/verify loop for a single developer in Claude Code, with adversarial review at every gate: plans and diffs get refuted by a fresh Claude subagent or a panel of outside models (OpenAI, Gemini, DeepSeek), not just approved. State lives in files, not the conversation, so you clear aggressively and keep both your context and your token bill lean.",
"version": "3.7.8",
"author": {
"name": "John Crenshaw"
},
"homepage": "https://github.com/crenshawdev/cadence",
"repository": "https://github.com/crenshawdev/cadence.git",
"license": "MIT",
"keywords": [
"planning",
"workflow",
"claude-code",
"software-development",
"git"
]
}
What ships with it
1 file beside plugin.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.
- yesterday First seen · 20 lines scan A 6b2fea200f9c
cadence is a plugin published in the GitHub repository crenshawdev/cadence (4 stars, last pushed 2d 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
alibabacloud-agent-toolkit
Plugin marketplace listing 3 plugins: alibabacloud-core, alibabacloud-spec-ops, alibabacloud-ecs-ops.
romek-plugins
Claude Code plugins by Roman Rozenberger.
dokumenty
Operacje na dokumentach: konwersja PDF/Office do Markdown (markitdown, opendataloader-pdf), redlining .docx z Track Changes (redline-docx-pl), anonimizacja i pseudonimizacja PII (let-it-be), terminy procesowe (terminy-procesowe-pl), klauzule umowne (klauzule-kontraktowe-pl), kalkulatory procesowe…
the-loop
Plugin marketplace listing 1 plugin: the-loop.
craft
Full-stack developer toolkit with integrated workflow automation - 48 commands, 2 agents, 41 skills with standardized dry-run preview mode (29 with --dry-run support). Code, git, site, docs, testing, architecture, CI, distribution, teaching workflows, planning, release pipeline, and ADHD-friendly features including…
cybrix-deploy
Deploy the current static site to a live HTTPS URL via Cybrix. Detects Next.js export, Astro, Vite, Hugo, Eleventy, and plain HTML. Returns a live URL on .cbrx.cc in under 60 seconds.