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 andregusman-raiz/a-gusman-claude --skill prd-writergit clone --depth 1 https://github.com/andregusman-raiz/a-gusman-claudeWrote 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/andregusman-raiz/a-gusman-claude/prd-writer)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/prd-writer"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/prd-writer/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/andregusman-raiz/a-gusman-claude/prd-writer"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/prd-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.01624 |
| Opus 5 | $0.00023 | $0.00812 |
| Sonnet 5 | $0.00009 | $0.00325 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
prd-writer 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 9d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Writer Skill
Criar PRDs (Product Requirements Documents) padronizados — o documento que antecede a SPEC tecnica.
PRD responde "O QUE e POR QUE". SPEC responde "COMO".
Docs Location (OBRIGATORIO)
PROJECT_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
[ "$PROJECT_ROOT" = "$HOME/Claude" ] && { echo "Erro: workspace raiz, nao projeto"; exit 1; }
DEST="$PROJECT_ROOT/docs/specs/{name}-prd.md"
NUNCA salvar em ~/Claude/docs/specs/ — bloqueado por hook. Detalhes: ~/Claude/.claude/shared/patterns/docs-location.md.
Naming Convention
- Feature:
$PROJECT_ROOT/docs/specs/{feature-name}-prd.md - Produto:
$PROJECT_ROOT/docs/specs/{product-name}-prd.md - Issue:
$PROJECT_ROOT/docs/specs/issue-{N}-prd.md
Template: PRD Completo
# PRD: [Titulo]
**Author**: [nome]
**Date**: YYYY-MM-DD
**Status**: Draft | Review | Approved
**SPEC**: (link para SPEC quando criada)
---
## 1. Problema
[1-3 frases. O que esta errado ou faltando? Qual dor do usuario resolve?]
## 2. Usuarios e Personas
| Persona | Descricao | Necessidade Principal |
|---------|-----------|----------------------|
| [nome] | [quem e, contexto] | [o que precisa] |
## 3. Escopo
### In Scope
- Item 1
- Item 2
### Out of Scope
- Item A (motivo ou issue futura)
- Item B (sera feito em fase posterior)
## 4. Requisitos Funcionais (alto nivel)
| ID | Requisito | Prioridade |
|----|-----------|------------|
| RF-01 | [descricao do que o sistema deve fazer] | Must |
| RF-02 | [descricao] | Must |
| RF-03 | [descricao] | Should |
| RF-04 | [descricao] | Could |
Prioridades: Must (obrigatorio), Should (importante), Could (desejavel), Won't (nao agora)
## 5. Requisitos Nao-Funcionais
| ID | Categoria | Requisito | Target |
|----|-----------|-----------|--------|
| RNF-01 | Performance | [descricao] | [metrica] |
| RNF-02 | Seguranca | [descricao] | [metrica] |
| RNF-03 | Acessibilidade | [descricao] | [metrica] |
| RNF-04 | Disponibilidade | [descricao] | [metrica] |
## 6. Metricas de Sucesso
Como saber que funcionou? (metricas mensuráveis, nao feelings)
| Metrica | Baseline (hoje) | Target | Como medir |
|---------|-----------------|--------|------------|
| [nome] | [valor atual] | [valor desejado] | [ferramenta/metodo] |
## 7. Riscos e Mitigacoes
| Risco | Probabilidade | Impacto | Mitigacao |
|-------|---------------|---------|-----------|
| [descricao] | Alta/Media/Baixa | Alto/Medio/Baixo | [como mitigar] |
## 8. Pesquisa e Referencias
- [Links para findings.md, benchmarks, concorrentes analisados]
- [Decisoes de produto ja tomadas e rationale]
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.
- 9d ago First seen · 170 lines · 47 tokens per session scan A e017c92cb03b
prd-writer is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 1,624 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-09-03.
Other skills, from other repositories
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.
retrospective-audit
Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles (bounded by auditbundlecap), re-derive the root cause and return one JSON object carrying a ranked findings array (one to three sub-patterns) — no edits, no worktree. Invoked as a subagent…
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
tmux-lane-orchestrator
Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.