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 bodangren/git-workflow --skill prd-authoringgit clone --depth 1 https://github.com/bodangren/git-workflowWrote 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/bodangren/git-workflow/prd-authoring)<a href="https://agentmods.dev/skills/bodangren/git-workflow/prd-authoring"><img src="https://agentmods.dev/badge/skills/bodangren/git-workflow/prd-authoring/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/bodangren/git-workflow/prd-authoring"><img src="https://agentmods.dev/badge/skills/bodangren/git-workflow/prd-authoring.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.00063 | $0.01698 |
| Opus 5.5 | $0.00025 | $0.00679 |
| Sonnet 5.5 | $0.00013 | $0.00340 |
| Haiku 4.5 | $0.00006 | $0.00170 |
Grade A, and why
prd-authoring 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 2mo 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Authoring Skill
Purpose
To accelerate and enhance early-stage project planning by using a powerful generative AI to create high-quality first drafts of key strategic documents. This skill integrates the Gemini CLI into the PRD authoring workflow, transforming it from a manual template-filling exercise into a dynamic, AI-assisted process.
The skill guides users from a vague project idea to a well-defined Product Requirements Document (PRD) by:
- Generating a Product Brief: Creates a comprehensive brief from a simple project name.
- Generating a Research Plan: Uses the product brief to generate a targeted research document.
- Generating a full PRD: Synthesizes the brief and research into a detailed PRD with objectives, requirements, and success criteria.
This approach bridges the gap between "we have an idea" and "we're ready to write specs" with unprecedented speed and quality.
When to Use
Use this skill in the following situations:
- Starting a new project from an initial concept.
- Generating a first draft of a product brief, research plan, or PRD.
- Validating an existing PRD against quality standards.
- Breaking down a PRD into epics for sprint planning.
Do NOT use this skill for:
- Implementation-level specifications (use spec-authoring instead).
- Sprint planning from approved specs (use sprint-planner instead).
Prerequisites
- Project initialized with AgenticDev structure (
docs/directory exists). geminiCLI tool installed and authenticated.
PRD Philosophy
Strategy Before Tactics: PRDs define WHAT we're building and WHY before specs define HOW we'll build it. This skill uses AI to rapidly generate the "WHAT" and "WHY" so that teams can focus on review, refinement, and strategic alignment.
Workflow Commands
The status Command
Purpose
Assess project readiness and provide guidance on next workflow steps. This is the recommended starting point.
Workflow
Run the status check to understand the current state of your PRD documents.
bash scripts/prd-authoring.sh status [project-name]
The script will report which documents exist (product-brief.md, research.md, prd.md, etc.) and recommend the next logical command to run.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .gitkeep 0 B
- examples/01-product-brief-example.md 7.3 KB
- examples/02-research-example.md 11 KB
- examples/03-prd-example-abbreviated.md 16 KB
- examples/IMPLEMENTATION_SUMMARY.md 11 KB
- examples/QUICK_START.md 8.4 KB
- examples/README.md 6.9 KB
- examples/workflow-test-log.md 12 KB
- scripts/prd-authoring.sh 50 KB runs code
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.
- 2mo ago First seen · 210 lines · 63 tokens per session scan A 67aa9a844b90
prd-authoring is a skill published in the GitHub repository bodangren/git-workflow (11 stars, last pushed 10mo ago), licensed MIT. It adds 63 tokens to every session and 1,698 once invoked, about $0.0003 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…