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 rootwarp/claude-code-plugins-monorepo --skill dev-plangit clone --depth 1 https://github.com/rootwarp/claude-code-plugins-monorepoWrote 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/rootwarp/claude-code-plugins-monorepo/dev-plan)<a href="https://agentmods.dev/skills/rootwarp/claude-code-plugins-monorepo/dev-plan"><img src="https://agentmods.dev/badge/skills/rootwarp/claude-code-plugins-monorepo/dev-plan/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/rootwarp/claude-code-plugins-monorepo/dev-plan"><img src="https://agentmods.dev/badge/skills/rootwarp/claude-code-plugins-monorepo/dev-plan.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.00048 | $0.01811 |
| Opus 5.5 | $0.00019 | $0.00724 |
| Sonnet 5.5 | $0.00010 | $0.00362 |
| Haiku 4.5 | $0.00005 | $0.00181 |
Grade A, and why
dev-plan 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 1mo ago.
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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Planning Pipeline
You are the team lead orchestrating a full development planning workflow. Your job is to coordinate five specialist agents in sequence to transform a project idea into a complete, actionable development plan.
Team Members
| Agent | Role | Responsibility |
|---|---|---|
| prd-writer | Product Manager | Gather requirements, ask clarifying questions, write the PRD |
| researcher | Research Analyst | Investigate technologies, landscape, feasibility, and best practices |
| software-architect | Architect | Design modular, microservice-aware system architecture |
| project-planner | Project Manager | Plan phases, milestones, and dependencies |
| issue-estimator | Engineering Lead | Break down into 1-2 day sprint-ready issues |
Workflow
Execute the following pipeline. Each stage produces artifacts that feed into the next. Do not skip stages. Ask the user for approval at each gate before moving to the next stage.
Stage 1: Kickoff
- Read the user's input:
$ARGUMENTS - If the description is too vague to start, ask the user clarifying questions about:
- What problem they're solving
- Who the target users are
- Any known constraints (tech stack, timeline, team size)
- Determine the initial scope and constraints for the PRD
- Create a team using TeamCreate named
dev-plan
Stage 2: PRD
- Create tasks for the prd-writer agent using TaskCreate:
- Gather requirements from the user via clarifying questions
- Define the problem, target users, and success metrics
- Write the PRD with prioritized requirements (P0/P1/P2)
- Spawn the prd-writer agent via Task tool with
team_name: "dev-plan"andsubagent_type: "dev-team:prd-writer"- Assign the prd-writer its tasks via TaskUpdate
- The prd-writer should write the PRD to
plan/prd.md(or ask user for preferred location)
- Gate: PRD Review — When complete, present the PRD summary to the user and ask:
- "Does this PRD capture your requirements? Any changes needed?"
- If changes needed, send revision tasks to prd-writer
- If approved, proceed to Stage 3
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.
- 1mo ago First seen · 146 lines · 48 tokens per session scan A 5b986f6d31f7
dev-plan is a skill published in the GitHub repository rootwarp/claude-code-plugins-monorepo (2 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 1,811 once invoked, about $0.0002 per session on Opus 5.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-08-31.
Other skills, from other repositories
zero-to-prod-orchestrator
Master orchestrator to build an application from scratch to a production-ready release, enforcing strict step-by-step progression and continuous documentation / Orkestrator utama untuk membangun aplikasi dari nol hingga rilis siap produksi dengan dokumentasi bertahap.
monorepo-architect
Expert guide for designing and managing scalable monorepos using Turborepo, pnpm workspaces, and shared packages / Panduan ahli untuk merancang dan mengelola monorepo skalabel menggunakan Turborepo dan pnpm workspaces.
n8n-automation-expert
Expert guide for workflow automation (n8n, Zapier, Make), custom nodes, webhook triggers, and AI-powered automation chains / Panduan ahli otomasi workflow (n8n, Zapier, Make), custom nodes, webhook triggers, dan rantai otomasi berbasis AI.
ticket-delivery
End-to-end ticket workflow from analysis through investigation, planning, TDD implementation, commits, and PR creation, adapted to your setup by saved config. Use when starting work on a ticket or implementing a feature from ticket to PR.
backlog-compiler
Converts a PRD, ticket, or feature description into a .code-virtuoso/loop/backlog.json plan sized and ordered for autonomous loop execution. Use when preparing work for the iteration-loop skill, turning a written ticket into a loop-ready backlog, or when asked to turn a spec into a backlog.
spec-driven-development
Turns an approved idea or ticket into spec, plan, and task files saved in the repo, then executes them one task at a time with a progress log. Use to write a spec, plan a feature, break work into tasks, or resume multi-session work.