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 marcoemrich/agentic_coding_lab --skill test-listgit 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/skills/marcoemrich/agentic_coding_lab/test-list)<a href="https://agentmods.dev/skills/marcoemrich/agentic_coding_lab/test-list"><img src="https://agentmods.dev/badge/skills/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/skills/marcoemrich/agentic_coding_lab/test-list"><img src="https://agentmods.dev/badge/skills/marcoemrich/agentic_coding_lab/test-list.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.00914 |
| Opus 5.5 | $0.00009 | $0.00366 |
| Sonnet 5.5 | $0.00004 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00091 |
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 — 119 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 comprehensive test list that covers every example and rule from the specification:
- Read
prompt.mdthoroughly -- every rule, every example, every clarifying question - Turn each example into at least one
it.todo()test case - Order tests from simplest to most complex
- Use
it.todo()only -- no executable tests yet
Context: $ARGUMENTS
Test List Creation Process
Step 1: Understand the Feature
Read the complete prompt.md specification. Pay special attention to
integration examples and clarifying questions (marked with ?) -- these
disambiguate rules that may seem open to interpretation in isolation.
- What are all operations the system must support?
- What rules govern each operation?
- Which examples in the spec illustrate these rules?
Step 2: Identify Test Cases from the Spec
Walk through the specification section by section. For each rule and each example:
- Create a test case that verifies the described behavior
- Include the expected numeric values from the spec in the test description
- If a clarifying question resolves an ambiguity, create a test for the clarified interpretation
- If the spec uses an example-mapping format (rules, examples, questions), every listed example must have a corresponding test
Step 3: Order Tests (Simple -> Complex)
Arrange tests in increasing complexity:
- Simplest case (often empty/zero/single item)
- Individual rules in isolation
- Rules with modifiers
- Combinations of multiple rules
- Multi-step scenarios (e.g., operations that reference earlier results)
Step 4: Write Test Descriptions
For each test case:
- Use
it.todo("description") - Include expected values:
"should return 115 G (100 base + 10 first-insurance + 5 fee)" - Be specific and unambiguous
- Reference the rule being tested
Step 5: Review Test List
Check for:
- Every spec example is covered by at least one test
- Every operation described in the spec has tests
- Every clarifying question has a corresponding test
- Tests are ordered simple -> complex
- Each test is independent
- Descriptions include expected values
- All tests use
it.todo()
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 · 119 lines · 22 tokens per session scan A 53ae84fbe200
test-list is a skill published in the GitHub repository marcoemrich/agentic_coding_lab (13 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 914 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…