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 agentmods add skills/rtazima/claude-proj-blueprint/implement-prdnpx skills add rtazima/claude-proj-blueprint --skill implement-prdgit clone --depth 1 https://github.com/rtazima/claude-proj-blueprintWrote 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/rtazima/claude-proj-blueprint/implement-prd)<a href="https://agentmods.dev/skills/rtazima/claude-proj-blueprint/implement-prd"><img src="https://agentmods.dev/badge/skills/rtazima/claude-proj-blueprint/implement-prd.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.00029 | $0.00666 |
| Opus 5 | $0.00015 | $0.00333 |
| Sonnet 5 | $0.00006 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
implement-prd 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 5d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement from PRD
Workflow
- Read the PRD completely in
docs/product/ - Check related ADRs in
docs/architecture/ - Check applicable specs in
docs/specs/(design, compliance, etc.) - Detect design flow — determine how UI will be built:
- Figma flow: PRD contains a Figma link → use Figma MCP server to extract design context (components, spacing, colors, layout) → implement matching the design
- Agent flow: PRD has no Figma link → activate
.claude/skills/frontend-agent/SKILL.md→ load design tokens fromdocs/specs/design-system/README.md→ scan existing components → generate UI from tokens + component library + PRD requirements
- Plan Mode — create implementation plan before coding
- Implement following
CLAUDE.mdconventions - Tests — create tests following
.claude/skills/testing/SKILL.md - Spec checks — verify compliance with active modules
- Document — update docs if needed
Design flow detection
Check the PRD for these patterns to determine the flow:
- Contains
figma.comURL or## Designsection with link → Figma flow - Contains
## Designwith "see design-system tokens" or no link → Agent flow - No design section at all → Agent flow (use tokens + existing patterns)
Rules
- Never implement without reading the full PRD first
- If the PRD is ambiguous, ask before assuming
- Always check if an ADR already exists for the technical decision
- Atomic commits per feature/sub-feature
- Never hardcode UI values — always use design tokens or Figma specs
Racionalizações comuns
| Racionalização | Realidade |
|---|---|
| "O código tá simples, não precisa de testes" | Código simples hoje vira complexo amanhã. Testes documentam intenção. |
| "Já sei o que o PRD quer, não preciso ler tudo" | PRDs têm restrições e edge cases nas entrelinhas. Leia completo. |
| "Esse ADR não se aplica aqui" | Se o ADR existe, alguém já enfrentou esse problema. Verifique antes de ignorar. |
| "Vou commitar tudo junto, é mais rápido" | Commits atômicos permitem revert cirúrgico. Commit grande = revert impossível. |
| "Design tokens são exagero pra esse componente" | Hardcode hoje, inconsistência amanhã. Sempre use tokens. |
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.
- 5d ago First seen · 52 lines · 29 tokens per session scan A d2c7095efebd
implement-prd is a skill published in the GitHub repository rtazima/claude-proj-blueprint (20 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 666 once invoked, about $0.0001 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-30.
Other skills, from other repositories
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.
modular-skills
Build composable skill modules with hub-and-spoke loading. Use when token budget is tight.
product-image-processor
Download, resize, and remove backgrounds from product images at scale. Use when the user asks to "process product images", batch-download images from the schedule, strip backgrounds, or standardize product photos.
tool-catalog
Show the available Architecture Studio skills and their host-appropriate commands, plus Claude Code's native Architecture Studio agents. Use when the user invokes tool-catalog, asks "what can you do" or "what skills are available", or wants a directory of plugin commands. Do not use for a host's native skill-list…