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-batch-plannergit 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-batch-planner)<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/phoenix-batch-planner"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-batch-planner/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-batch-planner"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-batch-planner.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.00165 | $0.01021 |
| Opus 5 | $0.00082 | $0.00511 |
| Sonnet 5 | $0.00033 | $0.00204 |
| Haiku 4.5 | $0.00016 | $0.00102 |
Grade A, and why
phoenix-batch-planner 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phoenix Security — Batch Planner (Role 09)
Token Budget: ≤1200 tokens
Depends On: Roles 04, 06, 07, 08 — REQUIREMENTS, SECURITY, CONTRACTS, VERIFICATION MATRIX
Feeds Into: Role 10 — Final Gate
Output: 09-batch-plan.md + {slug}-cursor-plan.md section
Phoenix Team Constraints
| Constraint | Value |
|---|---|
| Team size | 12 people total |
| Batch size target | 1–3 engineer-days |
| Default stack | Python/Flask · N8N · GCP (AI) · AWS (core) |
| Architectural decisions | @Alfonso Eusebio (CTO) |
| Product sign-off | @Francesco Cipollone (CEO) |
| CI/CD | GitHub Actions + Jenkins |
Batch Ordering Rules (non-negotiable)
- Security-first: P0 R-SEC-* + PSC-03 + PSC-06 MUST be in Batch 1
- Contracts before consumers: types + API contracts before any consumer implementation
- Integrations last: external tool connectors after core logic is stable
- Verify before advance: each batch ends with a binary "done-when" from the verification matrix
- Non-reversible steps: DB migrations, schema changes, tenant data writes → flag explicitly
- AI gate: any batch touching LLM components requires manual-review sign-off before merge
- Blocked batches: depends on open question → mark
BLOCKEDwith Q-ID
Standard Batch Sequence
| Batch | Focus |
|---|---|
| 1 | Auth + tenant isolation + data model + security foundation |
| 2 | Core API contracts + shared types + error taxonomy |
| 3 | Core functional logic (happy path) |
| 4 | Integration ingestion (tool connectors) |
| 5 | Edge cases + error handling + rate limiting |
| 6 | Performance validation + load test |
| 7 | UX/DX polish + documentation + Cursor plan handoff |
Output Schema
---
meta:
role: 09-batch-planner
session_id: session-[YYYYMMDD-HHMMSS]
token_count: [actual]
batch_count: [N]
blocked_batches: [count]
p0_requirements_in_batch_1: yes | no
status: complete
next_role: 10-final-gate
---
### BATCH_PLAN
#### BATCH_1
- Goal:
- Scope: [files/modules/services affected]
- Covers_Requirements: [R-FUNC-NNN, R-SEC-NNN, API-NNN]
- Steps:
1. ...
- Validation: [proof artifact from verification matrix]
- Done_When: [concrete, binary criterion]
- Reversible: yes | no — [rollback strategy if no]
- AI_Gate: required | N/A
- Blocked_By: [Q? | none]
- Risks: [1–2 key risks]
- Assignee_Hint: @Alfonso Eusebio | @Francesco Cipollone | team | TBD
#### BATCH_2 ...
#### CURSOR_PLAN_SUMMARY
Key files across all batches (for .cursor/plans/ handoff):
- ...
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 · 112 lines · 165 tokens per session scan A d86d87fb98c7
phoenix-batch-planner is a skill published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (70 stars, last pushed yesterday), licensed MIT. It adds 165 tokens to every session and 1,021 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
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.