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/sdlc-flownpx skills add douglance/sdlc-plugin --skill sdlc-flowgit clone --depth 1 https://github.com/douglance/sdlc-pluginWrote 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/douglance/sdlc-plugin/sdlc-flow)<a href="https://agentmods.dev/skills/douglance/sdlc-plugin/sdlc-flow"><img src="https://agentmods.dev/badge/skills/douglance/sdlc-plugin/sdlc-flow.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.00021 | $0.01422 |
| Opus 5 | $0.00010 | $0.00711 |
| Sonnet 5 | $0.00004 | $0.00284 |
| Haiku 4.5 | $0.00002 | $0.00142 |
Grade A, and why
sdlc-flow 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC Flow
The plugin is an optional graph of phases. Each phase is a skill that routes to one agent role and emits an artifact for its immediate receiver. This skill explains where to start, which dependencies apply, and how the phases connect.
Read references/core-ontology.md when reasoning about system entities, relationships, cardinalities, lifecycle edges, authority, traceability, evidence, or provider projections. The ontology controls relationships; project glossaries control term definitions.
Host routing contract
When the host exposes the named phase agents and you are the parent/orchestrator, delegate the selected phase to its named owner and pass the complete prior artifact. When already executing as that owner, or when named-agent delegation is unavailable, run the phase locally. Never delegate the same phase recursively. The artifact contract is portable; automatic delegation is a host capability, not something Rulesync can synthesize.
Lifecycle artifact contract
Use lifecycle-documentation for every phase output and input gate. Select the smallest applicable
IEEE/ISO information item, write it in STE-derived controlled English, preserve stable IDs, and end
with the required handoff block. A receiving phase must reject an incomplete artifact instead of
guessing what the producing phase meant.
The default path: idea → shipped
Select only the phases the work needs. Run selected phases in dependency order; each handoff passes one accepted artifact to one immediate receiver.
feasibility-analysis(→ researcher) — scout an unfamiliar problem space. Start here when the approach is unknown. Produces options, constraints, and trade-offs.requirements-gathering(→ product-owner) — turn a vague or high-blast-radius request into a stress-tested specification. Start here when what to build is unclear.planning(→ project-manager) — break the spec into a plan of milestones with dependencies, risks, and an explicit out-of-scope set. Produces a plan.design(→ architect) — settle interfaces, contracts, exact files, and trade-offs. Produces a technical design. For user-facing work, pair withvisual-design(→ graphic-designer) for layout, composition, states, and accessibility.implementation(→ engineer) — build it test-first in vertical slices. Produces tested, bounded changes. Commit those changes when the task includes commit authority.testing(→ tester) — adversarially falsify the change by executing it across edge cases, scale, and security. Produces a verdict with reproducible failing cases.quality(→ quality-engineer) — assure the change beyond execution: verification & validation, review/inspection, and the quality attributes. Produces a quality verdict.
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 · 105 lines · 21 tokens per session scan A a6b882005c46
sdlc-flow is a skill published in the GitHub repository douglance/sdlc-plugin (4 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,422 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…