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-implementgit 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-implement)<a href="https://agentmods.dev/skills/kgiwojno/g-sdd/g-implement"><img src="https://agentmods.dev/badge/skills/kgiwojno/g-sdd/g-implement.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.00077 | $0.07531 |
| Opus 5 | $0.00039 | $0.03766 |
| Sonnet 5 | $0.00015 | $0.01506 |
| Haiku 4.5 | $0.00008 | $0.00753 |
Grade A, and why
g-implement 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 8d 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 — 824 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Behavior
1. Check prerequisites
All prior pipeline stages must be complete before implementation.
Check if docs/features/ contains any feature directories.
If not, stop: "No feature found. Please run /g-prd first."
If there are multiple features, list them and ask which one to implement. If there's only one, use it.
Check the selected feature has all required artifacts:
PRD.md— if missing, stop: "No PRD. Please run /g-prd."PLAN.md— if missing, stop: "No plan. Please run /g-plan."TASKS.md— if missing, stop: "No tasks. Please run /g-tasks."
Check if AGENTS.md exists in the project root.
If not, stop: "No AGENTS.md. Please run /g-agents."
2. Load the task list and set up git
Read docs/features/[name]/TASKS.md. Parse all tasks, their
statuses, types (HITL/AFK), and dependencies (blocked by).
Task statuses and what they mean:
- Pending — ready to be picked up (if unblocked)
- In Progress — started but not finished (session may have been interrupted)
- Complete — done, AC passed, slice report written, review gate passed
- Blocked — couldn't finish, needs human decision
- REVIEW REQUIRED — review or self-report flagged something the user must decide (unmerged until settled)
- Skipped — deliberately deferred by user
Verify-and-switch to the feature branch. The feature branch
{feature-name} is created by /g-prd. This stage only
verifies it exists and switches to it; the orchestrator never
creates feature branches at this stage. The switch is silent —
invoking the stage implies the operator's intent.
Run this block literally. Do not paraphrase, shortcut on observation ("I can see we're already on the feature branch"), or skip when the current branch appears correct. The explicit run IS the spec compliance signal.
expected="{feature-name}" # from selected feature directory
current=$(git rev-parse --abbrev-ref HEAD)
if [ "$current" = "$expected" ]; then
: # already on it
elif git show-ref --verify --quiet "refs/heads/$expected"; then
git checkout "$expected"
else
echo "feature branch '$expected' missing — run /g-prd to create it"
exit 1
fi
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.
- 8d ago First seen · 824 lines · 77 tokens per session scan A 2677bd407346
g-implement is a skill published in the GitHub repository kgiwojno/g-sdd (6 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 7,531 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.