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 arozumenko/sdlc-skills --skill implement-featuregit clone --depth 1 https://github.com/arozumenko/sdlc-skillsWrote 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/arozumenko/sdlc-skills/implement-feature)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/implement-feature"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/implement-feature/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/arozumenko/sdlc-skills/implement-feature"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/implement-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 99 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00054 | $0.00884 |
| Opus 5.5 | $0.00022 | $0.00354 |
| Sonnet 5.5 | $0.00011 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
implement-feature scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Sanity check before running automated tests. API → `curl` the endpoint. UI → How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Implementation: Plan → Test → Build → Verify → Ship
Core philosophy: understand the plan, write tests first, implement to pass them, verify everything, ship clean.
Platform & systems
gh issue … / gh pr … below are the GitHub reference. Translate to your
tracker per .agents/profile.md § Project systems (jira / gitlab-issues /
azure-boards / linear) and your code host's CLI per .agents/workflow.md
(GitLab glab, Azure DevOps az repos, Bitbucket bb, Gitea tea). If scout
hasn't recorded them, ask before assuming GitHub.
The eight steps
1. Load the plan
2. Write test cases
3. Implement
4. Manual verification
5. Write automated tests
6. Run full test suite
7. Commit & PR
8. Document on ticket
1. Load the plan
gh issue view <N>. Identify acceptance criteria (definition of done),
interface contract (input/output types if defined), dependencies, and what's
explicitly in and out of scope. If anything is unclear, ask the tech-lead via
a subagent call or tracker comment before writing code. Post a 🔧 **Started** comment so the team
knows work is in progress.
2. Write test cases (TDD red phase)
Define "done" as executable tests before implementing. For each acceptance criterion, write a test. Cover happy path, error cases, edge cases. Run them and confirm they fail — that's the red phase.
3. Implement
Write the minimum code to pass the tests. Rules:
- Follow existing patterns — read similar features in the codebase first
- One change at a time — verify syntax after each file edit
- Match the interface contract exactly if the task defines one
- No scope creep — don't add features beyond the acceptance criteria
- Don't refactor neighbors — a feature task is not a cleanup task
- Don't optimize prematurely — make it work before making it fast
4. Manual verification
Sanity check before running automated tests. API → curl the endpoint. UI →
browser snapshot + interaction. Backend logic → one-liner that calls the
function. Catches the obvious breaks before test run.
What ships with it
2 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.
- 1mo ago First seen · 102 lines · 54 tokens per session scan A 93469abefefc
implement-feature is a skill published in the GitHub repository arozumenko/sdlc-skills (25 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 884 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.