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/helpnpx skills add lantisprime/claude-sdlc --skill helpgit 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/help)<a href="https://agentmods.dev/skills/lantisprime/claude-sdlc/help"><img src="https://agentmods.dev/badge/skills/lantisprime/claude-sdlc/help.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.00037 | $0.00659 |
| Opus 5 | $0.00018 | $0.00329 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
help 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Help — Plugin Reference
Read-only. Never writes files. Never modifies artifacts. Never invokes other skills.
Invocation modes
No args: /help
Print a condensed command list — one line each — then a usage tip. Screen budget: ≤ 20 lines total.
SDLC Plugin — command reference
/configure set up config/tools.json and config/tools.local.json
/start guided intake; fix-fast eligibility check; hands off to /plan
/plan Phase 1 — classify task, validate scope, estimate effort
/analyze Phase 2 — requirements with stable REQ IDs
/design Phase 3 — architecture bundle, tech specs, test cases
/build Phase 4 — code + unit tests, scoped to plan
/test Phase 5 — test execution, defects, UX conformance
/deploy Phase 6 — deployment proposal and supervised execution
/support Phase 7 — observability wiring (logging, alerts, dashboards)
/docs Phase 8 — docs refresh and traceability matrix
/status show in-flight task state and pending sign-offs (read-only)
/review cross-cutting diff review (correctness + security)
/fix-fast compressed path for small bug fixes only (≤2 files, ≤50 LOC)
Run /help <command> for detail on any command.
Run /help commands for the full reference table.
/help commands
Print the full command reference table.
Read each file in commands/ and extract the YAML description: field. Format as a markdown table: Command | Purpose. Sort by phase order: configure, start, plan, analyze, design, build, test, deploy, support, docs, status, review, fix-fast, token-review.
/help <command>
- Read
commands/<command>.md. Extract the YAMLdescription:field and the first non-frontmatter paragraph. - Read
skills/<command>/SKILL.mdif it exists. Extract the first non-frontmatter paragraph. - If neither file exists, print:
No help entry found for /<command>. - Assemble output (≤ 25 lines):
/<command> — <YAML description>
<first paragraph from commands/<command>.md or skills/<command>/SKILL.md>
Example:
/<command> <inferred one-liner>
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 · 68 lines · 37 tokens per session scan A 8055bb8a0e72
help is a skill published in the GitHub repository lantisprime/claude-sdlc (3 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 659 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
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.