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 mattmre/EVOKORE-MCP-PUBLIC --skill tddgit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/mattmre/evokore-mcp-public/tdd)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/tdd"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/tdd/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/mattmre/evokore-mcp-public/tdd"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/tdd.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.00025 | $0.00334 |
| Opus 5 | $0.00013 | $0.00167 |
| Sonnet 5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
tdd 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 7d 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
/tdd — Test-Driven Development
Enforces the Red-Green-Refactor TDD cycle: write failing tests first, implement to pass, then refactor.
Usage
/tdd "implement TrustLedger.record() method"
The TDD Cycle
Red (Write failing test)
Write a test that describes the desired behavior. Run it — it must fail:
npx vitest run --reporter=verbose tests/integration/TrustLedger.test.ts
Green (Make it pass)
Write the minimum implementation to make the test pass. No more.
Refactor (Clean up)
Clean up both the implementation and the test without changing behavior. Re-run tests — still green.
Done Criteria
- Tests written BEFORE implementation code
- All tests pass:
npx vitest run - TypeScript compiles:
npx tsc --noEmit - No implementation code without a corresponding test
Integration
- Pairs with
/verify-qualityto compute truth score - AGT-017 (Quality Engineer) tracks test-to-code ratio
- eval-harness PAT-002 measures test-before-commit compliance
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.
- 7d ago First seen · 47 lines · 25 tokens per session scan A 8315cf860d98
tdd is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 334 once invoked, about $0.0001 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
test-writing
Writes meaningful tests that actually catch bugs.
ai-observability-promptfoo
Testing and evaluation framework for LLM prompts and applications -- promptfooconfig.yaml, assertions, model-graded evals, red teaming, CI/CD integration, custom providers, and comparative evaluation.
fable-tdd
Drive testable behavior changes and bug fixes through disciplined red-green-refactor cycles with observable regression tests. Use when implementing new features with unit/integration tests, fixing reproducible bugs, modifying business logic, or writing test-first behavior contracts — even if the user does not…
add-tests
Generates tests for existing code. Analyzes the target function, method, or class to identify the happy path, error cases, and edge cases, then writes test cases following the project's testing framework and naming conventions. Invoked when the user asks to add tests, write tests, cover code, or increase coverage.
test-driven-development
Use when writing production code. Enforces RED-GREEN-REFACTOR cycle: write failing test, make it pass, improve design. Prevents test-after development and ensures verified behavior.
fable-mode
Compatibility alias for the canonical get-fable coding lifecycle. Use when the user explicitly asks for Fable mode or when an existing installation invokes this legacy skill name.