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/sigistry/marketplaceWrote 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/sigistry/marketplace/test-gap-analysis)<a href="https://agentmods.dev/commands/sigistry/marketplace/test-gap-analysis"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/test-gap-analysis/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/sigistry/marketplace/test-gap-analysis"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/test-gap-analysis.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.00013 | $0.02919 |
| Opus 5 | $0.00006 | $0.01460 |
| Sonnet 5 | $0.00003 | $0.00584 |
| Haiku 4.5 | $0.00001 | $0.00292 |
Grade A, and why
test-gap-analysis 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 5d 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 — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Gap Analysis Command
You are tasked with performing a comprehensive analysis of the codebase to identify gaps in test coverage. This analysis will help prioritize testing efforts and ensure critical code is properly tested.
Step 1: Discover the Codebase Structure
Perform a thorough scan of the project:
Identify Source Code
- Find all source code directories (src/, lib/, app/, etc.)
- Identify the programming language(s)
- Map the directory structure
- List all code files that should have tests
Identify Test Code
- Find all test directories (tests/, test/, tests/, spec/)
- Identify test files by naming conventions:
*.test.js,*.spec.ts,*_test.py,*_test.go,Test*.java
- Map test files to their corresponding source files
Identify Testing Framework
- Detect from
package.json,requirements.txt,pom.xml,go.mod - Look for: Jest, Pytest, JUnit, Go testing, RSpec, Mocha, etc.
Step 2: Analyze Source Files for Testable Units
For each source file, identify:
Functions and Methods
- Public functions
- Exported functions
- Class methods (public and protected)
- Utility functions
- API endpoints/route handlers
Classes
- Public classes
- Service classes
- Repository/DAO classes
- Controller classes
- Utility classes
Modules
- Module exports
- Public APIs
- Entry points
Step 3: Map Tests to Source Code
Create a mapping between source and tests:
For Each Source File:
-
Find corresponding test file
- Check naming conventions (file.ts → file.test.ts)
- Check test directories mirroring source structure
- Search for imports of the source file in test files
-
Analyze test coverage
- Which functions/methods have tests?
- How many tests per function?
- Are edge cases tested?
- Are error conditions tested?
-
Calculate coverage metrics
- Percentage of functions with at least one test
- Percentage of lines covered (if coverage data available)
- Number of test cases per function
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.
- 5d ago First seen · 423 lines · 13 tokens per session scan A e285687747d1
test-gap-analysis is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 5d ago), licensed MIT. It adds 13 tokens to every session and 2,919 once invoked, about $0.0001 per session on Opus 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-09-03.
Other commands, from other repositories
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
f5-gate
Quality gate management with evidence collection.
_test-shared
Shared testing patterns and templates (internal).
engineer
Guided full-project lifecycle - walks intake → plan (sign-off) → autonomous build → quality gates → CI/finish, invoking the right claude-engineer skill at each stage.
check-01-happy
Le wiki est dans un état sain : toutes les pages ont un frontmatter valide, les liens [[wikilinks]] pointent vers des pages existantes, index.md est à jour et aucune page n'est orpheline. La commande /check doit produire un rapport propre et mettre à jour wiki/log.md. Elle ne doit rien modifier dans le wiki au-delà du…
check-02-edge-stale-links
Le wiki contient des liens brisés (une page référence une autre qui a été renommée ou n'existe pas encore) et une page dont le champ lastupdated date de plus de 6 mois sans source récente correspondante. Le comportement attendu est que le librarian détecte et signale ces anomalies dans un rapport clair, sans les…