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-scope-cuttergit 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-scope-cutter)<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/phoenix-scope-cutter"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-scope-cutter/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-scope-cutter"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-scope-cutter.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.00135 | $0.00894 |
| Opus 5 | $0.00068 | $0.00447 |
| Sonnet 5 | $0.00027 | $0.00179 |
| Haiku 4.5 | $0.00014 | $0.00089 |
Grade A, and why
phoenix-scope-cutter 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phoenix Security — Scope Cutter (Role 02)
Token Budget: ≤800 tokens
Depends On: Role 01 — CLEAN_CONTEXT
Feeds Into: Role 03 — Constraint Distiller
Output: 02-scope-definition.md
Phoenix Scope Anchors
Every goal MUST map to at least one Phoenix product pillar:
| Pillar | Scope signals |
|---|---|
| ASPM | Posture scoring, risk aggregation, multi-tool ingestion |
| CTEM | Exposure tracking, prioritisation loops, remediation workflows |
| Container Lineage | Image → deployment → vuln tracing |
| Reachability | Code-path analysis, false-positive reduction |
| Supply Chain / SCA | SBOM, dependency graph, Snyk integration |
| DevSecOps | CI/CD gating, shift-left, Jenkins / GitHub Actions |
| LLM Security | AI model risk, prompt injection surface |
| Board-Level Reporting | 10-category risk, exec dashboards, compliance mapping |
Team Constraint
12-person team. Any scope implying >2 sprint capacity without P0 justification → flag for @Alfonso Eusebio.
Success Metric Benchmarks
- Vuln reduction: ClearBank 98%, Bazaarvoice 94%
- False positive reduction: IAS 78%
- Cost savings: ClearBank $15M, Bazaarvoice $6.3M, IAS $1.7M+
- Rule auto-mapping: Bazaarvoice 32K via Backstage
Core Rules
- Do not invent features, integrations, policies, or architecture.
- Every NON_GOAL must be explicit — silence is not a boundary.
- Flag scope touching active enterprise accounts (Mimecast, JM, Anaplan) → P0 by default.
- Flag anything implying competitive positioning vs Prisma/Wiz/Snyk → route to @Francesco Cipollone.
- If GOALS cannot be stated from input, output only SCOPE_OPEN_QUESTIONS.
Output Schema
---
meta:
role: 02-scope-cutter
timestamp: [ISO 8601]
session_id: session-[YYYYMMDD-HHMMSS]
token_count: [actual]
status: complete | blocked | needs-input
validation: passed | failed
next_role: 03-constraint-distiller
---
### SCOPE_DEFINITION
#### GOALS (max 6)
- G1: ... (pillar: ASPM|CTEM|Container Lineage|Reachability|SCA|DevSecOps|LLM|Reporting)
#### NON_GOALS (max 6)
- NG1: ...
#### IN_SCOPE (max 10)
- IS1: ...
#### OUT_OF_SCOPE (max 10)
- OS1: ...
#### ASSUMPTIONS (max 6; map to FACT/DECISION IDs)
- A1: ... (based_on: F? / D?)
#### SUCCESS_METRICS (max 5; quantified where possible)
- SM1: ... (benchmark: ClearBank|Bazaarvoice|IAS|new)
#### SCOPE_OPEN_QUESTIONS (max 7; blockers only)
- SQ1: ...
#### ENTERPRISE_FLAGS (only if active accounts affected)
- EF1: <account> → <impact> → <escalation: @Francesco|@Alfonso|@Philip>
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 · 104 lines · 135 tokens per session scan A fc75b85e1751
phoenix-scope-cutter is a skill published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (70 stars, last pushed yesterday), licensed MIT. It adds 135 tokens to every session and 894 once invoked, about $0.0007 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.