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 kgiwojno/g-sdd --skill g-prdgit clone --depth 1 https://github.com/kgiwojno/g-sddWrote 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/kgiwojno/g-sdd/g-prd)<a href="https://agentmods.dev/skills/kgiwojno/g-sdd/g-prd"><img src="https://agentmods.dev/badge/skills/kgiwojno/g-sdd/g-prd/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/kgiwojno/g-sdd/g-prd"><img src="https://agentmods.dev/badge/skills/kgiwojno/g-sdd/g-prd.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.00056 | $0.03268 |
| Opus 5 | $0.00028 | $0.01634 |
| Sonnet 5 | $0.00011 | $0.00654 |
| Haiku 4.5 | $0.00006 | $0.00327 |
Grade A, and why
g-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 10d 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Precondition
Before any other behavior, run:
[ -d .git ] && [ -d docs/templates ]
If either path is missing, print exactly:
Project not set up for the g-sdd pipeline. Run /g-setup first.
Then STOP. Do not proceed to any further step, do not explore the codebase, do not interview, do not propose a name. Do not vary the message based on which path is missing — diagnosis is the same.
Behavior
-
Check if
docs/RESEARCH.mdexists. If it does, read it and use it as context. If it doesn't, note that research is optional and proceed.Check if
CONTEXT.mdexists at the repo root. If it does, read it and use as context for the interview — the## Languageentries are the project's canonical vocabulary and should be reused (not redefined) during the conversation. IfCONTEXT.mdis absent (greenfield or pre-retrofit project), proceed without it; the interview will populate it from scratch in step 6.Run this read literally on every invocation. Do not skip the read on observation that the file looks empty or header-only — the explicit read IS the spec compliance signal.
Check if
docs/adr/contains any ADRs. If yes, read them and use as context during the interview. Reference existing decisions where relevant: "ADR-0001 chose PostgreSQL — does that still apply for this feature?"If during the interview the user indicates something that contradicts an existing ADR, capture it as a note in the PRD (e.g., "Note: this feature may require revisiting ADR-0002 (REST over GraphQL)").
/g-prddoes NOT modify existing ADRs; superseding or rewriting an existing ADR happens at/g-planstep 8 or/g-adr./g-prdMAY inline-draft NEWStatus: DraftADRs during the step 6 interview for filter-passing decisions (see step 6 for the discipline). This loosens the prior "PRD does NOT create ADRs" rule — under the three-criteria filter and the Draft lifecycle, PRD-time decisions that meet the filter capture rationale at peak interview fidelity rather than being deferred to/g-plan. Any Drafts created here flow through/g-planstep 6's promotion gate identically to step-4-drafted Drafts on the subsequent/g-planrun.
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.
- 10d ago First seen · 375 lines · 56 tokens per session scan A eb6b04e5fbb7
g-prd is a skill published in the GitHub repository kgiwojno/g-sdd (6 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 3,268 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…