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.
git clone --depth 1 https://github.com/marcoemrich/agentic_coding_labWrote 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/commands/marcoemrich/agentic_coding_lab/test-list)<a href="https://agentmods.dev/commands/marcoemrich/agentic_coding_lab/test-list"><img src="https://agentmods.dev/badge/commands/marcoemrich/agentic_coding_lab/test-list/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/commands/marcoemrich/agentic_coding_lab/test-list"><img src="https://agentmods.dev/badge/commands/marcoemrich/agentic_coding_lab/test-list.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.00000 | $0.00702 |
| Opus 5.5 | $0.00000 | $0.00281 |
| Sonnet 5.5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
test-list 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Test List Phase
You are now in the Test List Phase of TDD. Follow these instructions to create a comprehensive test list.
Your Mission
Create a test list using it.todo() for BASE FUNCTIONALITY ONLY:
- Identify the core/base functionality of the feature
- Break it down into discrete, testable behaviors
- Create test cases using
it.todo()- NO executable tests yet - Order tests from simplest to most complex
- Avoid advanced features or edge cases
Context: $ARGUMENTS
Test List Rules
What to Include (Base Functionality)
- Empty/zero cases: What happens with empty input?
- Single element cases: Simplest non-empty input
- Two element cases: Introduces interaction
- Multiple element cases: Generalizes the pattern
- Basic validation: Essential constraints only
What to Exclude (Save for Later)
- Advanced features
- Edge cases
- Performance optimizations
- Exotic inputs
- Error handling beyond basics
Process
Step 1: Understand the Feature
- What is the core functionality?
- What are the essential behaviors (not nice-to-haves)?
- What is the minimum viable feature?
Step 2: Identify Base Test Cases
List 3-6 test cases covering base functionality only.
Step 3: Order Tests (Simple → Complex)
- Simplest case (often empty/zero)
- Single element
- Two elements
- Multiple elements
- Basic validation
Step 4: Write Test File
Create the test file with it.todo() entries:
import { describe, it, expect } from "vitest";
import { functionName } from "./implementation.js";
describe("Feature Name", () => {
it.todo("should [simplest case]");
it.todo("should [next case]");
it.todo("should [more complex case]");
// ... ordered simple → complex
});
Step 5: Provide Summary
After creating the test list, output:
📋 Test List Created:
**Feature**: [feature name]
**Test File**: [filename].spec.ts
**Base Functionality Tests**: [count]
**Test Cases** (ordered simple → complex):
1. ✅ [first test description]
2. ✅ [second test description]
3. ✅ [third test description]
...
**Advanced Features** (NOT included):
- [feature 1] - save for later
- [feature 2] - save for later
**Next Step**: Invoke `/red` to activate the first test.
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 · 111 lines · 0 tokens per session scan A d396b5ab7b40
test-list is a command published in the GitHub repository marcoemrich/agentic_coding_lab (13 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 702 tokens. 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 commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.