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 djscheuf/agentic-dev-ecosystem-template --skill sdlc-implementgit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWrote 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/djscheuf/agentic-dev-ecosystem-template/sdlc-implement)<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/sdlc-implement"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/sdlc-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/djscheuf/agentic-dev-ecosystem-template/sdlc-implement"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/sdlc-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.00042 | $0.01250 |
| Opus 5.5 | $0.00017 | $0.00500 |
| Sonnet 5.5 | $0.00008 | $0.00250 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade A, and why
sdlc-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 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.
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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC Implement Workflow
Purpose
Implement planned functionality using Test-Driven Development (TDD) methodology by orchestrating skills and subworkflows.
Trigger
- After Planning an implementation, and before writing any production code
Inputs Required
- User Story Analysis Document (path to .json file)
- Implementation Plan for this Workstream (path to .json file)
- Relevant domain context
CRITICAL RULES
- FORBIDDEN: Writing production code directly - You MUST use the designated skills and subworkflows
- FORBIDDEN: Skipping skill invocations - Each phase requires specific skill/workflow invocation
- FORBIDDEN: Proceeding to next phase until current phase verification passes
- ONE priority group at a time - Complete all tests in a priority group before moving to next
Workflow Phases
Phase 0: Review Context
MANDATORY: Read all input documents before proceeding.
Required Inputs:
- User Story Analysis Document
- This Workstream's Implementation Plan
- Existing Test Cases Document (if any from previous run)
- Relevant domain context (vault pages, existing code)
Actions:
- Read and understand the requirements
- Identify what needs to be built
- Note any dependencies or constraints
Output: Mental model of the task (no files created)
Phase 1: Design Test Cases
MANDATORY: INVOKE the design-test-cases skill.
FORBIDDEN:
- Write test cases manually
- Skip this step if test cases already exist (review them instead)
Skill to Invoke: design-test-cases
Expected Output:
- Test cases JSON file at path specified in sentinel file
- Sentinel file:
<input_parent>/.process/design-test-cases.done.json, retained after verification (repository-root fallback only when there is no input path)
Verification:
- Confirm test cases file exists and follows schema
- Confirm sentinel file exists
- Review test cases for completeness
Before Proceeding: Ensure verification passes.
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 Changed c3a1edbd8d7f
- 1mo ago First seen · 173 lines · 42 tokens per session scan A 5392c1db7866
sdlc-implement is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 20d ago), licensed MIT. It adds 42 tokens to every session and 1,250 once invoked, about $0.0002 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-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.
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.
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…