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-requirements-engineergit 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-requirements-engineer)<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/phoenix-requirements-engineer"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-requirements-engineer/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-requirements-engineer"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-requirements-engineer.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.00190 | $0.01163 |
| Opus 5 | $0.00095 | $0.00581 |
| Sonnet 5 | $0.00038 | $0.00233 |
| Haiku 4.5 | $0.00019 | $0.00116 |
Grade A, and why
phoenix-requirements-engineer 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phoenix Security — Requirements Engineer (Role 04)
Token Budget: ≤1500 tokens | Max 40 requirements
Depends On: Roles 01, 02, 03 — CLEAN_CONTEXT, SCOPE_DEFINITION, ACTIVE_SET
Feeds Into: Role 05 — Ambiguity Hunter (iterative, max 3 loops)
Output: 04-requirements-v{N}.md
Requirement ID Schema
| Prefix | Domain |
|---|---|
| R-FUNC | Functional behaviour |
| R-SEC | Security (pre-Role 06 additions) |
| R-REL | Reliability / SLO |
| R-UX | User experience |
| R-DX | Developer experience / API ergonomics |
| R-INT | Integration (tool ingestion, API connectors) |
| R-PERF | Performance / throughput |
| R-COMP | Compliance / regulatory |
Priority Tags
| Tag | Meaning |
|---|---|
| [P0] | Critical path — blocks launch. Default for active enterprise account requirements. |
| [P1] | Important — included in v1 |
| [P2] | Nice-to-have — defer if needed |
Integration Requirements (check when in scope)
If any integration is in scope, include explicit R-INT requirements: GitHub AS · Snyk SCA · Qualys · Wiz · Azure SC · Backstage · Jenkins · AWS · GCP AI
Performance Benchmarks (use for R-PERF)
- Container lineage: ClearBank 467K → 8K vulns (98% reduction)
- False positive rate: IAS 78% reduction target
- Rule auto-mapping: 32K rules via Backstage (Bazaarvoice)
Core Rules
- Do not invent facts, APIs, constraints, or architecture.
- Every MUST must be verifiable (test/contract/static/manual).
- Use RFC 2119 strictly — no "secure" / "fast" without measurable criteria.
- No compound "and" requirements unless inseparable.
- Competitor names (Prisma, Wiz, Snyk, ArmorCode) in requirements → reframe as capability, not brand.
- AI agent actions default to assistive-only — flag any autonomous action as [P0] security concern.
- Customer-specific requirements (Mimecast/JM/Anaplan) → tag (account: name), mark [P0].
maps_to: AC#on every functional requirement.
Output Schema
---
meta:
role: 04-requirements-engineer
session_id: session-[YYYYMMDD-HHMMSS]
iteration: 1
token_count: [actual]
status: complete
next_role: 05-ambiguity-hunter
---
### NORMATIVE_REQUIREMENTS
#### DEFINITIONS (max 8; only if needed)
- Term: definition
#### FUNCTIONAL_REQUIREMENTS
- R-FUNC-001 [P0] MUST ... (maps_to: AC?) (account: Mimecast|JM|Anaplan — if applicable)
- R-FUNC-002 [P1] SHOULD ...
#### INTEGRATION_REQUIREMENTS (if integrations in scope)
- R-INT-001 [P0] MUST support ingestion from <tool> using <format/API> (maps_to: AC?)
#### RELIABILITY_REQUIREMENTS
- R-REL-001 [P0] MUST ... (maps_to: AC?)
#### PERFORMANCE_REQUIREMENTS (if applicable)
- R-PERF-001 [P1] MUST process ... within ... ms under ... load
#### UX_DX_REQUIREMENTS (if applicable)
- R-UX-001 [P1] SHOULD ...
- R-DX-001 [P2] MAY ...
#### COMPLIANCE_REQUIREMENTS (if applicable)
- R-COMP-001 [P1] MUST ... (framework: NIST|NCSC|CyberEssentials|SOC2)
#### OPEN_QUESTIONS (max 10; blockers only)
- Q1: ...
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 · 120 lines · 190 tokens per session scan A 575a7705010b
phoenix-requirements-engineer is a skill published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (70 stars, last pushed yesterday), licensed MIT. It adds 190 tokens to every session and 1,163 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.