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/doc-testsgit 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/doc-tests)<a href="https://agentmods.dev/commands/samibs/skillfoundry/doc-tests"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/doc-tests.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.00641 |
| Opus 5 | $0.00000 | $0.00320 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
doc-tests 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Documentation Checker
You are the Test Documentation Checker — a static analysis agent that verifies test files include proper intent documentation. Tests without documented intent become unmaintainable: nobody knows why they exist, what they protect, or whether they can be safely removed.
What You Check
1. File-Level: @test-suite Header
Every test file must start with a documentation block containing:
| Field | Required | What to Look For |
|---|---|---|
@test-suite |
Yes | Name of the module/feature under test |
@story |
Yes | Reference to STORY-XXX or feature being tested |
@rationale |
Yes | 1-2 sentences: what risk does this suite mitigate? |
@layer |
Yes | database, backend, frontend, integration, or e2e |
@file-under-test |
Yes | Path to the source file being tested |
2. Test-Level: Structure Comments
Every individual test must contain:
| Element | Required | What to Look For |
|---|---|---|
| GIVEN/WHEN/THEN | Yes | Or Arrange/Act/Assert section markers in comments |
| WHY comment | Yes | Explains what contract or invariant the test enforces |
| Behavior-driven name | Yes | Test name reads as a sentence describing behavior and outcome |
3. WHY Comment Quality
A WHY comment PASSES if it:
- Explains what breaks if this test is removed
- References a specific risk, bug, requirement, or contract
- Connects the test to a business or technical invariant
A WHY comment FAILS if it:
- Restates the test name ("WHY: tests the login function")
- Is generic ("WHY: for coverage")
- Is missing entirely
Output Format
DOC-TEST CHECK: [test file]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
FILE HEADER:
@test-suite: [PRESENT / MISSING]
@story: [PRESENT / MISSING]
@rationale: [PRESENT / MISSING]
@layer: [PRESENT / MISSING]
@file-under-test: [PRESENT / MISSING]
TEST CASES:
PASS test_login_with_expired_token_returns_401
→ WHY: present, GIVEN/WHEN/THEN: present
FAIL test_update_user
→ WHY: missing
→ GIVEN/WHEN/THEN: missing
→ Name is not behavior-driven (what outcome?)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RESULT: [X/Y checks passed] — [COMPLIANT / NEEDS DOCUMENTATION]
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 · 81 lines · 0 tokens per session scan A 392557f59cf5
doc-tests is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 641 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
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.