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-constraint-distillergit 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-constraint-distiller)<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/phoenix-constraint-distiller"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-constraint-distiller/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-constraint-distiller"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-constraint-distiller.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.00164 | $0.00881 |
| Opus 5 | $0.00082 | $0.00441 |
| Sonnet 5 | $0.00033 | $0.00176 |
| Haiku 4.5 | $0.00016 | $0.00088 |
Grade A, and why
phoenix-constraint-distiller 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phoenix Security — Constraint Distiller (Role 03)
Token Budget: ≤700 tokens
Depends On: Role 02 — SCOPE_DEFINITION
Feeds Into: Role 04 — Requirements Engineer
Output: 03-active-set.md
Phoenix Standing Constraints (PSC)
Evaluate all for inclusion. Include only those relevant to the current feature.
| ID | Constraint | Type | Proof Hint |
|---|---|---|---|
| PSC-01 | AWS = onboarding + core; GCP = Phoenix CTI + AI/LLM | operational | config/IaC |
| PSC-02 | Team = 12 people; no feature assumes >2 dedicated engineers | operational | planning |
| PSC-03 | Multi-tenant: customer data MUST be isolated at storage + query layer | security | test + static |
| PSC-04 | API ingestion MUST support: GitHub AS, Snyk, Qualys, Wiz minimum | functional | contract test |
| PSC-05 | Vuln prioritisation MUST incorporate reachability, not CVSS-only | functional | test |
| PSC-06 | All new endpoints MUST authenticate via Phoenix auth layer | security | static + test |
| PSC-07 | No direct competitor brand names in user-facing copy | compliance | manual review |
| PSC-08 | AI agents: assistive-only, disabled by default, no autonomous data ingestion | security | test + manual |
| PSC-09 | Customer data ingestion requires explicit opt-in | security/compliance | contract + manual |
| PSC-10 | Phoenix brand: ≤2 accent colors per visual; RFC 2119 in all specs | ux/doc | manual |
| PSC-11 | Container lineage: image build → registry → deployment MUST be preserved | functional | test |
| PSC-12 | Regulatory hooks: US (NIST) and UK (NCSC, Cyber Essentials) documented | compliance | manual |
Core Rules
- Constraints must be actionable and testable.
- No duplicates — merge overlapping constraints.
- No "nice-to-have" fluff.
- Do not invent constraints; if suspected but unconfirmed → CONSTRAINT_OPEN_QUESTIONS.
- Always include ≥1 security constraint (PSC-03 or PSC-06 or equivalent).
- Always include ≥1 operational constraint reflecting team size (PSC-02 or equivalent).
- If PSC-03 not included and feature touches customer data → flag as blocker.
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 · 86 lines · 164 tokens per session scan A 250d5941c7cb
phoenix-constraint-distiller is a skill published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (70 stars, last pushed yesterday), licensed MIT. It adds 164 tokens to every session and 881 once invoked, about $0.0008 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…