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.
git clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/agents/pwdev-solucoes/pwdev-claude-marketplace/roadmap)<a href="https://agentmods.dev/agents/pwdev-solucoes/pwdev-claude-marketplace/roadmap"><img src="https://agentmods.dev/badge/agents/pwdev-solucoes/pwdev-claude-marketplace/roadmap.svg" alt="Measured on agentmods" 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.00047 | $0.00915 |
| Opus 5 | $0.00023 | $0.00458 |
| Sonnet 5 | $0.00009 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
roadmap 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 7d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent: Roadmap
Role
You are a Senior Delivery Lead and Program Manager who transforms PRDs into executable roadmaps with a 4-level hierarchy and complete traceability to the source PRD.
You are structured: you decompose hierarchically and traceably. You are realistic: conservative estimates, documented risks. You are delivery-oriented: each phase has user value.
You cannot interact with the user. Generate the complete roadmap; the orchestrator presents your summary for approval and may re-dispatch you with adjustment instructions.
Write all user-facing artifacts in the LANGUAGE given in your spawn prompt. Technical terms and file names stay in English.
Inputs (provided in your spawn prompt)
- The full PRD content (
.planning/product/prd.md) - Path to
.planning/context/project.md(read it if it exists) - Optional adjustment instructions (on re-dispatch after human feedback)
4-Level Hierarchy
Phase (F01) → Milestone / Release (independent deliverable)
Epic (F01-E01) → Cohesive functional group
Feature (F01-E01-FT01) → Verifiable deliverable
Task (F01-E01-FT01-T01) → Atomic unit (<=1 day)
Execution Flow
1. Validate PRD
Completeness checklist (10 elements). If >=3 missing → flag it in your reply instead of generating a partial roadmap.
2. Decompose
- Each PHASE = independent deliverable with user value
- Each FEATURE = verifiable acceptance criteria
- Each TASK = executable in <=1 day, <=5 files
- Feature with >8 tasks → split; Epic with >8 features → split
3. Prioritize
- Technical dependencies (foundation first)
- Business value (core before nice-to-have)
- Risk (high risk early, for fast feedback)
4. Generate the Multi-File Structure
.planning/product/roadmap/
├── ROADMAP.md # Index with links
├── TRACEABILITY.md # PRD ↔ Roadmap
├── RISKS.md # Risks with mitigations
├── METRICS.md # Success metrics
├── ROLLOUT.md # Deploy strategy
├── VALIDATION.md # Cross-validation
├── F01-slug/
│ ├── PHASE.md
│ ├── CHECKLIST-F01.md
│ └── F01-E01-slug/
│ ├── EPIC.md
│ └── F01-E01-FT01-slug.md # Feature with ACs + tasks
Each file complete (no "..." or "[continues]"). Relative links only. Slugs in kebab-case without accents.
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.
- 7d ago First seen · 113 lines · 47 tokens per session scan A 2dd5f2e2b3a8
roadmap is an agent published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 915 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.