Borrowing it
Nothing to install: this file belongs to rmjosea/agentic-sdlc-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rmjosea/agentic-sdlc-kit/main/.agents/skills/implement/SKILL.mdgit clone --depth 1 https://github.com/rmjosea/agentic-sdlc-kitWrote 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/rmjosea/agentic-sdlc-kit/implement)<a href="https://agentmods.dev/skills/rmjosea/agentic-sdlc-kit/implement"><img src="https://agentmods.dev/badge/skills/rmjosea/agentic-sdlc-kit/implement/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/rmjosea/agentic-sdlc-kit/implement"><img src="https://agentmods.dev/badge/skills/rmjosea/agentic-sdlc-kit/implement.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.00072 | $0.00891 |
| Opus 5.5 | $0.00029 | $0.00356 |
| Sonnet 5.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 2mo 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.
- 2mo 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 3mo ago), licensed MIT. It adds 72 tokens to every session and 891 once invoked, about $0.0003 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
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…