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/davistroy/claude-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/davistroy/claude-marketplace/test-project)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/test-project"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/test-project/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/davistroy/claude-marketplace/test-project"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/test-project.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.00031 | $0.03609 |
| Opus 5 | $0.00015 | $0.01804 |
| Sonnet 5 | $0.00006 | $0.00722 |
| Haiku 4.5 | $0.00003 | $0.00361 |
Grade A, and why
test-project 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 — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fully Test Project Command
Execute a comprehensive test-fix-ship workflow that ensures high test coverage, passes all tests, and ships the changes via a PR.
Overview
This command implements an iterative test-driven workflow:
- Verify/achieve target coverage (default 90%)
- Run ALL tests using parallel sub-agents
- Fix any failures and repeat until all pass
- Update documentation, clean up, create PR
- Merge only if
--auto-mergeflag is provided; otherwise leave PR open for review
Input Validation
Required Arguments:
- None (operates on the current project)
Optional Arguments:
--coverage <n>- Target coverage percentage (default: 90). Example:--coverage 80--auto-merge- Automatically merge the PR after creation. Without this flag, the PR is created but left open for review.
Usage:
/test-project
/test-project --coverage 80
/test-project --auto-merge
/test-project --coverage 85 --auto-merge
Before proceeding, verify:
- This is a git repository with test infrastructure present
- GitHub CLI (
gh) is installed and authenticated (rungh auth status) - A test framework is configured (check for test config files and test files)
- The project has a package manager or build tool installed
If any of these prerequisites are missing, inform the user what needs to be set up before running this command.
Instructions
Execute the phases below in sequence. Each phase builds on the previous.
Phase 0: Scope Confirmation Gate
Before making any changes, gather and present the following to the user:
- Test frameworks detected - which test runner(s) and coverage tool(s) are present
- Current coverage - run coverage analysis and report the baseline percentage (if measurable)
- Files that will be modified - list source and test directories that are in scope
- Target coverage - the target percentage (from
--coverageflag or default 90%) - Auto-merge status - whether
--auto-mergewas specified
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 · 470 lines · 31 tokens per session scan A aa3a0ab8377e
test-project is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 3,609 once invoked, about $0.0002 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-04.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.