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 agentmods add skills/chianw/c31/gsd-progressnpx skills add ChianW/C31 --skill gsd-progressgit clone --depth 1 https://github.com/ChianW/C31Wrote 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/chianw/c31/gsd-progress)<a href="https://agentmods.dev/skills/chianw/c31/gsd-progress"><img src="https://agentmods.dev/badge/skills/chianw/c31/gsd-progress.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 | $0.00038 | $0.00780 |
| Opus 5 | $0.00019 | $0.00390 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
gsd-progress 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 3d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multilingual Triggers
| Language | Trigger phrases |
|---|---|
| EN | progress, next step, what next, 下一步, 继续, gsd-progress, where are we |
| ZH | 下一步, 继续, 进度 |
| JA | 次のステップ, 進捗確認 |
Output language: Respond automatically in the user's conversation language.
gsd-progress — Next-Step Detector
Detect where the project stands and suggest (or auto-execute) the next GSD command.
When to Use
- User says "progress", "next step", "what next", "下一步", "继续", or runs
gsd-progress - After completing a phase and the user needs direction
Workflow
Step 1: Read Planning Files
Read memory/.planning/STATE.md and memory/.planning/ROADMAP.md.
If either file is missing, stop and report:
No active project found. Run `gsd-new-project` first to initialize planning artifacts.
Step 2: Detect Current Phase
From STATE.md, extract:
Phase: the numeric or named phase (e.g., "0", "1", "Exploration")Status: pending / discussed / planned / executed / verified / shipped
If Status is not explicitly stated, infer from the content:
- "Active Tasks: None yet." or no tasks marked done → pending
- Tasks exist but no implementation details → discussed
- Plan or task list is present and not yet executed → planned
- Code has been written or files modified → executed
- Review or testing completed → verified
- Deployed or released → shipped
Step 3: Determine Next Command
| Status | Suggestion |
|---|---|
| No project (files missing) | gsd-new-project |
| pending | C31-brainstorm or gsd-discuss-phase |
| discussed | C31-plan or gsd-plan-phase |
| planned | C31-work or gsd-execute-phase |
| executed | C31-review or gsd-verify-work |
| verified | gsd-ship |
| shipped | "Project is shipped. Run gsd-new-project for a new project." |
Step 4: Suggest or Execute
Check for --auto flag in arguments, or if the user message contains "auto".
What ships with it
1 file 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.
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.
- 3d ago First seen · 87 lines · 38 tokens per session scan A 99852f807bfd
gsd-progress is a skill published in the GitHub repository ChianW/C31 (1 stars, last pushed 8d ago), licensed MIT. It adds 38 tokens to every session and 780 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-08-31.
Other skills, from other repositories
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
create-harness
Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a…
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
example-harness
Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming…
oia-manifest
Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture. Self-describes the harness's MCP wiring, witness signing, audit log, identity posture (always 'none' at v0.1). --check verifies an existing manifest, --dry-run prints without writing, --json emits to stdout.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.