Borrowing it
Nothing to install: this file belongs to doncheli/don-cheli-sdd. 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/doncheli/don-cheli-sdd/main/.agent/skills/doncheli-implement/SKILL.mdgit clone --depth 1 https://github.com/doncheli/don-cheli-sddWrote 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/doncheli/don-cheli-sdd/doncheli-implement)<a href="https://agentmods.dev/skills/doncheli/don-cheli-sdd/doncheli-implement"><img src="https://agentmods.dev/badge/skills/doncheli/don-cheli-sdd/doncheli-implement.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.1 | $0.00053 | $0.00250 |
| Opus 5 | $0.00026 | $0.00125 |
| Sonnet 5 | $0.00011 | $0.00050 |
| Haiku 4.5 | $0.00005 | $0.00025 |
Grade A, and why
doncheli-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 8d 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.
What it actually says
Don Cheli: TDD Implementer
Iron Law #1: TDD is MANDATORY
Every piece of production code MUST have a test written BEFORE the implementation.
Cycle
- RED: Write a test that FAILS
- GREEN: Write MINIMUM code to make the test pass
- REFACTOR: Clean up without changing behavior
Rules
- Never skip tests
- Never mark a task complete if stubs exist (
// TODO,throw new Error('not implemented')) - Run linter after each task
- Check coverage >= 85% on new code
- If a test fails 3 times, STOP and ask the user (Stop-Loss rule)
Quality Gates
- Gate 5: All tasks have TDD pairs (test + implementation)
- Gate 6: All tests pass, coverage met, lint clean, build succeeds
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.
- 8d ago First seen · 26 lines · 53 tokens per session scan A 1984310f1893
doncheli-implement is a skill published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 28d ago), licensed Apache-2.0. It adds 53 tokens to every session and 250 once invoked, about $0.0003 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-30.
Other skills, from other repositories
plan-pipeline-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
linked-intent-dev
Guide for linked-intent development (LID). Consult for ALL code changes. Walks changes through a mode-aware six-phase workflow (HLD → LLD → EARS → intent-narrowing edge audit → tests-first → code) with mandatory stops between each phase. Bugs walk the arrow like any other change — no short-circuit. Enforces cascade…
test-validator
Validates test coverage, quality, and TDD compliance. Detects weakened assertions, deleted tests, and tautological patterns. Auto-invoke when user has written code and needs test validation.
fix-issue
Fix a GitHub issue following project coding standards. Creates branch, implements fix with TDD, and prepares PR.
testing-patterns
Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.
agent-tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.