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/clawforgeai/clawforge/testgit clone --depth 1 https://github.com/ClawForgeAI/clawforgeWrote 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/clawforgeai/clawforge/test)<a href="https://agentmods.dev/commands/clawforgeai/clawforge/test"><img src="https://agentmods.dev/badge/commands/clawforgeai/clawforge/test.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.00331 |
| Opus 5 | $0.00000 | $0.00166 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
test 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 today.
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.
What it actually says
Smart Test Runner
Run tests with intelligent package filtering and reporting.
Instructions
Parse the test target from: $ARGUMENTS
Package detection
If no target specified, detect which package to test based on recently changed files using git diff --name-only HEAD~1 or git diff --name-only (for uncommitted changes).
- Files in
plugin/→ run plugin tests - Files in
server/→ run server tests - Files in
admin/→ run admin tests - Files across multiple packages → run all affected
- If no changes detected → ask the user which package to test
Commands by package
- plugin:
pnpm --filter @clawforgeai/clawforge test - server:
pnpm --filter @ClawForgeAI/clawforge-server test - admin:
pnpm --filter @ClawForgeAI/clawforge-admin test - all: run all three in sequence
With coverage
If the user asks for coverage, append -- --coverage:
pnpm --filter <package> test -- --coverage
Watch mode
If the user asks for watch mode:
pnpm --filter <package> test -- --watch
Single file
If $ARGUMENTS contains a file path, detect the package from the path and run:
pnpm --filter <detected-package> test -- <relative-path>
After running, summarize: total tests, passed, failed, skipped, and any failures with file paths.
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.
- today First seen · 45 lines · 0 tokens per session scan A c1b920e22201
test is a command published in the GitHub repository ClawForgeAI/clawforge (17 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 331 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-04.
Other commands, from other repositories
spec
Manage specifications in our development process.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.constitution
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
status
Run a full MCPWorks platform status check using the admin function suite via mcpmcpworks-runexecute.
checklist
Generate a custom checklist for the current feature based on user requirements.