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-rungit 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-run)<a href="https://agentmods.dev/skills/kgiwojno/g-sdd/g-run"><img src="https://agentmods.dev/badge/skills/kgiwojno/g-sdd/g-run/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-run"><img src="https://agentmods.dev/badge/skills/kgiwojno/g-sdd/g-run.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.00070 | $0.00637 |
| Opus 5 | $0.00035 | $0.00318 |
| Sonnet 5 | $0.00014 | $0.00127 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
g-run 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 12d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Behavior
1. Check project is initialized
Check if docs/features/ and docs/templates/ exist. If not,
run /g-setup first, then continue.
2. PRD phase
Run /g-prd. This will:
- Ask for the problem description
- Propose and approve a feature name
- Explore the codebase
- Interview relentlessly
- Sketch modules
- Write PRD.md
Remember the approved feature name — all subsequent stages use the same feature directory.
After PRD is written, confirm: "PRD complete. Moving to planning phase."
3. Plan phase
Run /g-plan for the same feature. This will:
- Read the PRD just created
- Explore codebase (technical patterns)
- Interview on durable technical decisions
- Draft vertical slices
- Quiz on the breakdown
- Write PLAN.md
After plan is written, confirm: "Plan complete. Moving to task generation."
4. Tasks phase
Run /g-tasks for the same feature. This will:
- Read PLAN.md + PRD.md
- Generate self-contained task per slice
- Present draft for review
- Write TASKS.md
After tasks are written, confirm: "Tasks complete. Moving to agent configuration."
5. Agent config phase
Run /g-agents. This will:
- Read PLAN.md + PRD.md
- Examine codebase conventions
- Generate AGENTS.md
- Present for review
- Write AGENTS.md
After AGENTS.md is written, confirm: "Agent config complete."
6. Checkpoint before implementation
Present a summary:
═══════════════════════════════════════
Feature: [name]
PRD: docs/features/[name]/PRD.md ✓
Plan: docs/features/[name]/PLAN.md ✓
Tasks: docs/features/[name]/TASKS.md ✓
Agents: AGENTS.md ✓
[N] tasks ready ([M] AFK, [K] HITL)
═══════════════════════════════════════
Ready to start implementation? (yes / no)
If no: end the session. The user can resume later with
/g-implement.
If yes: proceed to implementation.
7. Implementation phase
Run /g-implement for the same feature. This will:
- Show the dashboard
- Loop: pick task → spawn subagent → review report
- Handle HITL, REVIEW REQUIRED, Blocked, lessons learned
- Continue until all tasks done or user stops
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.
- 12d ago First seen · 97 lines · 70 tokens per session scan A 7e98cd8cd8a0
g-run is a skill published in the GitHub repository kgiwojno/g-sdd (6 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 637 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…
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…