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 lantisprime/claude-sdlc --skill startgit 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/start)<a href="https://agentmods.dev/skills/lantisprime/claude-sdlc/start"><img src="https://agentmods.dev/badge/skills/lantisprime/claude-sdlc/start/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/lantisprime/claude-sdlc/start"><img src="https://agentmods.dev/badge/skills/lantisprime/claude-sdlc/start.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.00107 | $0.03627 |
| Opus 5.5 | $0.00043 | $0.01451 |
| Sonnet 5.5 | $0.00021 | $0.00725 |
| Haiku 4.5 | $0.00011 | $0.00363 |
Grade A, and why
start 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 1mo 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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start — Opt-in Activation, Re-enable, and Task Intake
Read the marker state first. The path taken depends entirely on which marker files exist.
Marker state dispatch
| State | Condition | Path |
|---|---|---|
| Fresh install | .claude/sdlc/.enabled absent AND .claude/sdlc/.suspended absent |
Activate → Steps 0–4 |
| Suspended | .claude/sdlc/.suspended present |
Re-enable → Steps R1–R5 |
| Already enabled | .claude/sdlc/.enabled present |
Hand off to /plan |
Check .claude/sdlc/.suspended first. If present, go to the re-enable path even if .enabled also somehow exists — .suspended wins.
PATH A — Fresh Install (Steps 0–4)
Step 0 — Config check and auto-detection
Skip this step entirely if config/tools.json already exists.
Run the following detections silently — no prompts, just observe:
| Signal | Detected value |
|---|---|
.git directory |
vcs: "git" |
git remote get-url origin |
repo slug (owner/repo) |
.github/workflows present |
ci: "github-actions" |
.gitlab-ci.yml present |
ci: "gitlab-ci" |
.circleci/config.yml present |
ci: "circleci" |
Jenkinsfile present |
ci: "jenkins" |
package.json present |
language: "node" |
pyproject.toml or requirements.txt |
language: "python" |
go.mod present |
language: "go" |
Cargo.toml present |
language: "rust" |
pom.xml or build.gradle |
language: "java" |
jest or vitest in devDependencies |
test.command |
pytest in pyproject.toml |
test.command |
eslint in devDependencies |
lint.command |
ruff in pyproject.toml |
lint.command |
Remote URL contains github.com |
tracker: "github" |
Remote URL contains gitlab |
tracker: "gitlab" |
Remote URL contains bitbucket |
tracker: "bitbucket" |
Show detected values as facts, not questions. Then ask up to three prompts:
Prompt 1 — Tracker confirm (always shown, pre-selected if detected):
Issue tracker (inferred: GitHub Issues) — correct? [Y/n/override]
If remote is absent or ambiguous:
Which issue tracker does this project use?
A) GitHub Issues B) GitLab C) Jira D) Linear E) None
(detected: none) _
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.
- 1mo ago First seen · 382 lines · 107 tokens per session scan A d01de806b078
start is a skill published in the GitHub repository lantisprime/claude-sdlc (3 stars, last pushed 5mo ago), licensed MIT. It adds 107 tokens to every session and 3,627 once invoked, about $0.0004 per session on Opus 5.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
moai-workflow-thinking
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.
xcode-workflows
Xcode build system guidance for xcodebuild operations. Use when building iOS projects, running tests, analyzing build failures, or configuring schemes. Covers build/clean/test operations, interpreting xcodebuild output, and troubleshooting common build errors.
check-pr
Read-only inspection of a single GitHub PR lifecycle — checks CI, review feedback (threads, review bodies, top-level comments), description sync, and mergeability, and returns PASS or FAIL with per-gate findings. Never invokes the merge button. Use when verifying a PR is ready to merge, polling lifecycle progress…
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.
goga-define-resolve
Resolve product-level conflicts discovered during the definition process.
review-depth
Experimental declared review depth for linked-intent development. Use when a LID project's instruction file declares a review depth in prose (e.g. "Review depth - I review through LLD; below that, consolidate to one review") or the user asks to batch phase reviews, consolidate stops, or let go below a phase depth.…