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 agentmods add commands/marcoemrich/agentic_coding_lab/test-listgit clone --depth 1 https://github.com/marcoemrich/agentic_coding_labWhat 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 | $0.00000 | $0.00702 |
| Opus 5 | $0.00000 | $0.00351 |
| Sonnet 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 2d 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.
- 2d 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 (11 stars, last pushed 15d 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.