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/douglance/sdlc-plugin/lifecycle-documentationnpx skills add douglance/sdlc-plugin --skill lifecycle-documentationgit clone --depth 1 https://github.com/douglance/sdlc-pluginWhat 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.00029 | $0.00864 |
| Opus 5 | $0.00015 | $0.00432 |
| Sonnet 5 | $0.00006 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
lifecycle-documentation 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 2d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lifecycle Documentation
Create the smallest lifecycle artifact that lets the next phase work without guessing. Use the information model of the applicable IEEE/ISO standard. Do not add ceremonial sections that do not help a decision, action, or verification.
Preserve point-to-point ownership at each selected lifecycle edge. Do not combine artifacts owned by different phases, skip an immediate receiver, or address one handoff to multiple downstream phases. The lifecycle graph can branch between handoffs. Standards tailoring can combine information only when one phase owns all combined content.
Read references/standards-and-style.md before you select the artifact type or claim standards alignment. It contains the lifecycle map, the controlled-English profile, and current standard status.
Workflow
- Select the artifact type from the phase map in the reference.
- Confirm that one phase owns the artifact and that it names only the next receiver.
- Record the governing standard, its version, and all tailoring decisions.
- Write the artifact with the controlled-English profile below.
- Link inputs, requirements, decisions, implementation units, tests, and evidence with stable IDs.
- Apply the handoff gate. Return an explicit rejection note when required input is absent.
Controlled-English profile
Use an STE-derived profile. Do not claim full ASD-STE100 conformance unless the official standard, dictionary, and a conformance review are available.
- Use one term for one concept. Define project-specific terms once.
- Name the actor. Use active voice unless the actor is unknown.
- Write one instruction or requirement per sentence.
- Keep procedures at 20 words or fewer per sentence when practical.
- Keep descriptions at 25 words or fewer per sentence when practical.
- Put one topic in each paragraph. Use lists for complex conditions.
- Do not omit the subject, verb, or article to make text shorter.
- Replace vague words with a value, condition, owner, date, or measurable threshold.
- Use declared uppercase BCP 14 keywords for project requirements. Preserve
shallonly when a governing external standard or contract requires it. - Do not use
and/or. Split the cases or name the exact logical operator.
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.
- 2d ago First seen · 96 lines · 29 tokens per session scan A 6ac7dc847561
lifecycle-documentation is a skill published in the GitHub repository douglance/sdlc-plugin (4 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 864 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…