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 Dannykkh/skill-olympus --skill test-driven-developmentgit clone --depth 1 https://github.com/Dannykkh/skill-olympusWrote 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/dannykkh/skill-olympus/test-driven-development)<a href="https://agentmods.dev/skills/dannykkh/skill-olympus/test-driven-development"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/test-driven-development/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/dannykkh/skill-olympus/test-driven-development"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/test-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
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 →
- medium MCP Rug Pull · line 26 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 38 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 27 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 39 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00047 | $0.02671 |
| Opus 5.5 | $0.00019 | $0.01068 |
| Sonnet 5.5 | $0.00009 | $0.00534 |
| Haiku 4.5 | $0.00005 | $0.00267 |
Grade A, and why
test-driven-development 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development (TDD)
Overview
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
Violating the letter of the rules is violating the spirit of the rules.
Step 0: 테스트 프레임워크 자동 감지
TDD 시작 전 프로젝트의 테스트 환경을 감지합니다:
# 프레임워크 감지
_TEST_CMD=""
[ -f "package.json" ] && grep -q "vitest" package.json && _TEST_CMD="npx vitest run"
[ -f "package.json" ] && grep -q "jest" package.json && _TEST_CMD="npx jest"
[ -f "pytest.ini" ] || [ -f "pyproject.toml" ] && grep -q "pytest" pyproject.toml 2>/dev/null && _TEST_CMD="pytest"
[ -f "pom.xml" ] && _TEST_CMD="mvn test"
[ -f "*.csproj" ] && _TEST_CMD="dotnet test"
[ -f "go.mod" ] && _TEST_CMD="go test ./..."
echo "TEST_CMD: ${_TEST_CMD:-감지 실패 — 사용자에게 확인}"
| 감지 패턴 | 프레임워크 | 단일 파일 실행 | 전체 실행 |
|---|---|---|---|
| vitest in package.json | Vitest | npx vitest run path/to/test.ts |
npx vitest run |
| jest in package.json | Jest | npx jest path/to/test.ts |
npx jest |
| pytest.ini / pyproject.toml | pytest | pytest path/to/test.py |
pytest |
| pom.xml | JUnit/Maven | mvn test -pl module -Dtest=TestClass |
mvn test |
| *.csproj | xUnit/NUnit | dotnet test --filter ClassName |
dotnet test |
| go.mod | Go testing | go test ./pkg/... |
go test ./... |
| 없음 | - | 사용자에게 확인 | - |
파일 위치 컨벤션:
| 프레임워크 | 테스트 파일 위치 | 네이밍 |
|---|---|---|
| Vitest/Jest | src/__tests__/ 또는 *.test.ts |
{name}.test.ts |
| pytest | tests/ |
test_{name}.py |
| JUnit | src/test/java/ |
{Name}Test.java |
| xUnit | *.Tests/ |
{Name}Tests.cs |
| Go | 같은 디렉토리 | {name}_test.go |
The Iron Law
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
Write code before the test? Delete it. Start over.
No exceptions:
- Don't keep it as "reference"
- Don't "adapt" it while writing tests
- Don't look at it
- Delete means delete
What ships with it
1 file 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 · 359 lines · 47 tokens per session scan A 1aaad7684ba8
test-driven-development is a skill published in the GitHub repository Dannykkh/skill-olympus (7 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 2,671 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-09-03.
Other skills, from other repositories
audit-runner
Autonomous audit runner (separate sessions, no context limit). Use when: "audit-runner", "autonomous audit", "audit automatically".
refactor-team
Launch parallel refactoring agents: one restructures code in an isolated worktree, one writes tests to lock behavior, one reviews the result. Use when: "refactor team", "refactor-team", "safe refactor", "restructure code".
tdd
Use when the user wants test-driven development, asks to write tests first, or mentions TDD.
debug-team
Launch parallel debugging agents for systematic root-cause analysis. Use when: "debug team", "help me debug", "debug-team", "find the bug".
django-tdd
Django testing strategies with pytest-django, TDD methodology, factoryboy, mocking, coverage, and testing Django REST Framework APIs.
react-web
React web development with hooks, React Query, Zustand.