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/lantisprime/claude-sdlc/statusnpx skills add lantisprime/claude-sdlc --skill statusgit clone --depth 1 https://github.com/lantisprime/claude-sdlcWrote 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/lantisprime/claude-sdlc/status)<a href="https://agentmods.dev/skills/lantisprime/claude-sdlc/status"><img src="https://agentmods.dev/badge/skills/lantisprime/claude-sdlc/status.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.00067 | $0.01868 |
| Opus 5 | $0.00034 | $0.00934 |
| Sonnet 5 | $0.00013 | $0.00374 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
status 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 4d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status
Print the current task state so the human knows exactly where they are and what's next — without reading four directories themselves.
What this skill reads
.claude/sdlc/plans/— active plan and whether it has a signed gate.claude/sdlc/gates/— active gate, which phase it covers, whether it is signed.claude/sdlc/sign-offs/— which sign-off files have landed (if any)
This skill writes nothing. It never modifies any artifact.
Step 1 — Identify the active plan
Scan .claude/sdlc/plans/*.md, excluding versioned files (*.v1.md, *.v2.md, etc. — any file matching *.v[0-9]*.md). Versioned files are superseded archives; the active plan is always the unversioned <slug>.md file.
If the directory is absent or no non-versioned files exist, print:
No active task found.
Next: run /start or /plan to begin a task.
and stop.
If multiple non-versioned plan files exist, use the most recently modified one.
Step 2 — Identify the active gate
Scan .claude/sdlc/gates/*.md. Gate filenames follow the pattern <phase>-<task-slug>.md.
Map phase names to order: plan=1, analyze=2, design=3, build=4, test=5, deploy=6, support=7. Select the gate with the highest phase number. Break ties by taking the most recently modified file.
A gate is signed if its content contains a non-empty Signed at: field. A gate is unsigned if that field is absent, blank, or holds a placeholder.
If no gates exist yet, the active gate is "none" — the plan has been drafted but not yet signed.
Step 3 — Determine sign-off state
Sign-off rendering applies only when all three conditions hold:
- An active, signed gate exists.
- That gate contains a
## Required sign-offsblock (a markdown list of role names). .claude/sdlc/sign-offs/exists as a directory.
If any condition is unmet, skip the sign-off line entirely.
Extract required roles — parse the ## Required sign-offs block as a markdown bullet list. Each item is a role name (e.g. security, product, compliance).
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.
- 4d ago First seen · 173 lines · 67 tokens per session scan A 040c93d1c629
status is a skill published in the GitHub repository lantisprime/claude-sdlc (3 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 1,868 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
setup
Guide the user through verifying Grainulator's MCP servers are running, explain what each server does, handle optional dependencies, and initialize a first sprint if none exists. Use when the plugin is first installed, when MCP servers fail to connect, or when the user asks for help setting up Grainulator.
challenge
Adversarial testing of a specific claim. Try to disprove it.
harvest
Sprint analytics — type distributions, stale claims, velocity, prediction scoring.
healthcheck
Fast pre-flight health check for all Grainulator MCP servers. Pings each server once, reports status in a table, and provides exact fix commands for any that are down. Use before starting any Grainulator session to avoid wasting time on MCP disconnections.
orchard
Multi-sprint orchestration — view dependency graph, dispatch next ready sprint.
blind-spot
Structural gap analysis -- find what the sprint has not considered.