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/rmjosea/agentic-sdlc-kit/implementnpx skills add rmjosea/agentic-sdlc-kit --skill implementgit clone --depth 1 https://github.com/rmjosea/agentic-sdlc-kitWhat 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.00072 | $0.00891 |
| Opus 5 | $0.00036 | $0.00445 |
| Sonnet 5 | $0.00014 | $0.00178 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
implement 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement a Bounded Change
Complete one bounded outcome at a time and leave the repository in a verifiable state.
Select and bound
- Read
AGENTS.md, the selected source artifacts, and only required contracts. - Select exactly one valid input:
- a
readytask fromtasks.md: re-read task state, confirm every dependency isdone, then transition it toin-progress; - one bounded, decision-complete outcome from an approved spec or plan that does not require a task graph: state the selected outcome and artifact evidence;
- a direct-path change: confirm every direct-path condition in
AGENTS.mdand stateIntent,Change, andVerificationinline.
- a
- Inspect the affected code and tests before editing.
- State the outcome, intended change surface, and validation.
- Stop for a material ambiguity; do not invent product or architecture choices.
If execution changes how, update the durable plan or inline approach. When
a design change affects task boundaries, dependencies, validation, or change
surfaces, mark affected tasks stale and run decompose-tasks again before
continuing. If execution changes what, stop and reconfirm the accepted
intent; amend a spec when one exists or the expanded scope requires one. Mark
affected durable work stale.
Execute
- Make the smallest coherent change that satisfies the task.
- Follow existing repository conventions before introducing new patterns.
- Avoid unrelated cleanup and speculative abstraction.
- Work in short edit-run-observe loops.
- Preserve compatibility unless the approved plan says otherwise.
- Treat external input, secrets, permissions, and destructive effects as trust boundaries.
Read references/testing.md when selecting or writing tests. Read references/debugging.md only when a failure is not explained by the current change.
Verify
Run the narrowest useful checks during iteration, then all outcome-relevant checks before completion. Compare observed behavior with authoritative intent and the applicable artifact or inline evidence.
What ships with it
3 files 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 · 83 lines · 72 tokens per session scan A 2b6f2c818254
implement is a skill published in the GitHub repository rmjosea/agentic-sdlc-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 891 once invoked, about $0.0004 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.