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/Security-Phoenix-demo/security-skills-claude-codeWrote 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/security-phoenix-demo/security-skills-claude-code/phoenix-readiness-reviews)<a href="https://agentmods.dev/plugins/security-phoenix-demo/security-skills-claude-code/phoenix-readiness-reviews"><img src="https://agentmods.dev/badge/plugins/security-phoenix-demo/security-skills-claude-code/phoenix-readiness-reviews/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/security-phoenix-demo/security-skills-claude-code/phoenix-readiness-reviews"><img src="https://agentmods.dev/badge/plugins/security-phoenix-demo/security-skills-claude-code/phoenix-readiness-reviews.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
phoenix-readiness-reviews 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
{
"$schema": "https://www.schemastore.org/claude-code-plugin-manifest.json",
"name": "phoenix-readiness-reviews",
"version": "1.0.0",
"description": "Two adversarial review gates. plan-readiness-review asks whether a PRD, spec or RFC is implementable without inventing anything. production-readiness-review asks whether the code is actually built, wired, tested and safe to deploy, backed by a deterministic repo scanner.",
"author": { "name": "Phoenix Security", "email": "[email protected]", "url": "https://phoenix.security" },
"homepage": "https://github.com/Security-Phoenix-demo/security-skills-claude-code",
"repository": "https://github.com/Security-Phoenix-demo/security-skills-claude-code",
"license": "MIT",
"keywords": ["review", "prd", "spec-review", "production-readiness", "qa", "code-review", "ship-gate"]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 476 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 12 lines scan A 7fa3ba9722ec
phoenix-readiness-reviews is a plugin published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (70 stars, last pushed yesterday), 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-09-11.
Other plugins, from other repositories
crap-analyzer
Analyze recently-changed code for Change Risk Anti-Patterns. Computes CRAP per changed function across TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, and PHP. Auto-discovers how the repo generates coverage and proposes refactors + test stubs.
mattpocock-skills
Skills adapted from Matt Pocock's public collection.
superpowers-orchestrator
Agentic development framework for Claude Code — disciplined workflow routing, TDD enforcement, safety hooks, systematic debugging, and code review.
atlas-review
Takes the open pull requests of the Atlas/Bella monorepo from arrival to reviewed, fixed, merged, pushed and reported. The review itself is code-review:code-review, which is read-only, so resolving what it finds is this skill's own stage and the reason it exists. Lands by rebase rather than merge commit, pulls so…
stone-giant
Production-tested skills from Stone Giant Studio — artifact scoring, shutdown rituals, npm evaluation and security, CI/CD speedups, React Router v7, JavaScript/TypeScript, PostgreSQL/SQL Server/Drizzle/Kysely databases, testing, UI design, auth, AWS serverless, PDF generation, technical and marketing writing, product…
asynkron-devtools
ASYNKRON developer tools — profiler, test runner, code duplication detector, line counter, Roslynator, strict .NET standards, pre-PR checklist, continue-loop, test bomb and layered test methodologies.