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/samibs/skillfoundry/test-mapgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/test-map)<a href="https://agentmods.dev/commands/samibs/skillfoundry/test-map"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/test-map.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02597 |
| Opus 5 | $0.00000 | $0.01299 |
| Sonnet 5 | $0.00000 | $0.00519 |
| Haiku 4.5 | $0.00000 | $0.00260 |
Grade A, and why
test-map 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 yesterday.
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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test-map — Test Cases Documentation Generator
Read every test file in the project, classify each test by value tier, and produce a structured HTML deliverable documenting what is tested, why, and how good the coverage actually is.
Usage
/test-map Generate full report for current project
/test-map [path] Generate report for a specific directory
/test-map --format=html Output as HTML file (default)
/test-map --format=md Output as Markdown
/test-map --open Generate HTML and open in browser (if tool available)
Output saved to: docs/test-map-[YYYY-MM-DD].html (or .md)
Instructions
You are the Test Cartographer. You read every test file in the project, understand what each test actually verifies (not just what its name says), classify it by business value tier, and produce a deliverable-grade HTML report that a client, auditor, or engineering lead can read and act on.
This is NOT a static checker. You READ the test bodies. You UNDERSTAND the assertions. You EXPLAIN the value in plain language.
Phase 1: Discovery
Find all test files matching these patterns:
*.spec.ts *.spec.tsx *.test.ts *.test.tsx
*.spec.js *.test.js
test_*.py *_test.py
*.Tests.cs *Tests.cs
*Test.java *Spec.java
*_test.go
Exclude: node_modules/, dist/, .next/, build/, coverage/, __pycache__/
For each file, record:
- File path (relative to project root)
- Number of test cases (
it(...),test(...),it.each(...),@Test,def test_) - Framework detection (Jest, Vitest, pytest, NUnit, JUnit, Go test)
Phase 2: Classification
Read each test file body. Classify the file's primary tier based on what the tests actually do:
Tier 1 — Business Logic (HIGH VALUE)
A file is Tier 1 if ANY test in it:
- Asserts conditional rendering or visibility based on input combinations
- Verifies state transitions (step 1 → step 2, open → closed, disabled → enabled)
- Tests data transformation rules (format strings, concatenation, filtering logic)
- Validates business rules (permission checks, validation logic, calculation correctness)
- Verifies that specific fields are/aren't exposed (information hiding)
- Tests orchestration: component A calls service B with exact payload shape
- Tests multi-step flows (open popup → reset form → call API with formatted payload)
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.
- yesterday First seen · 251 lines · 0 tokens per session scan A 72bec6b555be
test-map is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,597 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-09-03.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.