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.
npx skills add Security-Phoenix-demo/security-skills-claude-code --skill phoenix-final-gategit 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/skills/security-phoenix-demo/security-skills-claude-code/phoenix-final-gate)<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/phoenix-final-gate"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-final-gate/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/skills/security-phoenix-demo/security-skills-claude-code/phoenix-final-gate"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-final-gate.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.00198 | $0.00951 |
| Opus 5 | $0.00099 | $0.00476 |
| Sonnet 5 | $0.00040 | $0.00190 |
| Haiku 4.5 | $0.00020 | $0.00095 |
Grade A, and why
phoenix-final-gate 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phoenix Security — Final Gate Reviewer (Role 10)
Token Budget: ≤800 tokens
Depends On: All previous roles (01–09)
Feeds Into: FEATURE_SPEC.md + Confluence push (if SHIP)
Output: 10-final-gate.md
Hard Blockers (any = NO_SHIP)
Run this checklist explicitly — do not skip any item:
- Critical ambiguities remaining (Role 05) > 0
- Any MUST lacks proof path (Role 08,
unverified_musts > 0without downgrade rationale) - PSC-03 multi-tenancy not addressed in security requirements
- PSC-06 auth layer not addressed for any new endpoint
- PSC-08 AI agent autonomous action not gated (if LLM in scope)
- Scope creep: requirements outside SCOPE_DEFINITION from Role 02
- P0 security requirements NOT in Batch 1 (Role 09)
- Active enterprise account requirements (Mimecast/JM/Anaplan) not covered at P0
Soft Warnings (flag, do not block)
- Manual-only proof paths for non-security requirements
- Missing success metrics vs Phoenix case study benchmarks
- Batch count implies >4 weeks without CTO sign-off
- Regulatory hooks not documented
- Competitor brand names in user-facing copy
Output Schema
---
meta:
role: 10-final-gate
session_id: session-[YYYYMMDD-HHMMSS]
token_count: [actual]
decision: SHIP | NO_SHIP
blocker_count: [N]
status: complete
---
### FINAL_GATE
#### DECISION
SHIP | NO_SHIP
#### HARD_BLOCKER_CHECK
- PSC-03 multi-tenancy: addressed | missing
- PSC-06 auth: addressed | missing
- PSC-08 AI agent: addressed | N/A
- Critical ambiguities: [count]
- Unverified MUSTs: [count]
- Scope creep: detected | none
- P0 in Batch 1: yes | no
- Enterprise account coverage: complete | gaps → [list gaps]
#### BLOCKERS (max 10; NO_SHIP only)
- B1: <gap> → source role: 0N → fix required: <exact action>
#### NON_BLOCKING_IMPROVEMENTS (max 10)
- N1: ...
#### NEXT_ACTIONS (ordered; owner + ETA)
1. [@owner] <action> — <ETA>
Post-Gate Actions
On SHIP:
- Save
10-final-gate.md - Compile
FEATURE_SPEC.md(Phoenix PRD template) - Push to Confluence SPM space (Atlassian MCP — mandatory; fallback parent: 1273987073)
- Ask once: "Want me to create Linear/Asana tickets, notify Slack, or email stakeholders?"
- Status: ✅ Pipeline complete
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 · 105 lines · 198 tokens per session scan A 73460c7d2bc8
phoenix-final-gate is a skill published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (70 stars, last pushed yesterday), licensed MIT. It adds 198 tokens to every session and 951 once invoked, about $0.0010 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-09-11.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…