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 markoblogo/abvx-agent-skills --skill test-driven-executiongit clone --depth 1 https://github.com/markoblogo/abvx-agent-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/markoblogo/abvx-agent-skills/test-driven-execution)<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/test-driven-execution"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/test-driven-execution/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/markoblogo/abvx-agent-skills/test-driven-execution"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/test-driven-execution.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.00066 | $0.00407 |
| Opus 5 | $0.00033 | $0.00204 |
| Sonnet 5 | $0.00013 | $0.00081 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
test-driven-execution 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 9d 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
Test Driven Execution
Use tests as the feedback loop that shapes the implementation one vertical slice at a time.
Core Rules
- Test behavior through public interfaces.
- Prefer integration-style tests over implementation-coupled tests.
- Work in vertical slices, not horizontal batches.
- One failing test -> one minimal implementation -> repeat.
- Refactor only while green.
Workflow
- Confirm the behavior to build or fix.
- Identify the highest useful seam to test.
- Write one failing test for one observable behavior.
- Implement the minimum code to make it pass.
- Repeat for the next behavior.
- Refactor only after the slice is green.
For a diagnosed regression that needs durable proof, capture the exact same targeted command before and after with bug-evidence-protocol, then capture relevant broader checks. Do not infer FIX_PROVEN from a green targeted test alone.
Anti-Pattern
Do not write all tests first and all code later. That produces test suites for imagined behavior instead of validated behavior.
Good Tests
- name the user-visible behavior;
- survive internal refactors;
- avoid private methods and internal collaborator trivia;
- verify what the system does, not how it does it.
Planning Questions
- Which behaviors matter most?
- Which seams already exist?
- What should not be tested at this layer?
- What prior art already exists in the repo?
Final Report
Include the behaviors covered, the seams used, what remains untested, and any refactor opportunities exposed by the loop.
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.
- 9d ago First seen · 54 lines · 66 tokens per session scan A 67a79ad24a1e
test-driven-execution is a skill published in the GitHub repository markoblogo/abvx-agent-skills (16 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 407 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-09-03.
Other skills, from other repositories
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
testing
Characterization testing and safety-net backfill for existing code. Use when legacy, under-tested, or risky code needs tests before a refactor, bug fix, or behavior change. Captures current behavior through public interfaces, identifies coverage gaps, and adds focused unit, integration, or E2E tests without replacing…
autonomous-tdd-debugger
Empowers the agent to autonomously run tests, read terminal stack traces, and self-heal code until tests pass. Transforms the agent from a passive coder to an active CI pipeline debugger.
debugging
Investigate failures whose root cause is still unknown — narrow the search space, instrument, and test falsifiable hypotheses. Use for intermittent or environment-dependent behavior, unexplained stack traces, regressions with no known trigger, or any symptom without a confirmed cause. Ends once the root cause is…
testing
Strategy and rules for writing or improving automated tests. Use when adding tests, improving coverage, fixing flaky tests, setting up a test suite, or deciding what and how to test. Emphasizes deterministic tests, testing behavior over implementation, and a tight validation loop. For diagnosing production failures…
bug-fix
Regression-first workflow for fixing a defect whose cause is known. Reproduce the confirmed defect, fix the root cause minimally, protect it with a regression test, and verify. If the root cause is still unknown, use the debugging skill first.