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/sandeep-alluru/groundcrew/testgit clone --depth 1 https://github.com/sandeep-alluru/groundcrewWhat 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.00157 |
| Opus 5 | $0.00000 | $0.00078 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
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 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.
Copies of this mod
8 near-identical copies found in the catalogue:
What it actually says
Run the full test suite with coverage and report results.
Steps:
- Run:
make test(equivalent to:pytest tests/ --cov=<name> --cov-report=term-missing) - Report:
- Total tests, passed, failed, skipped
- Coverage percentage — flag if below 85%
- Any failing tests: show the test name, error message, and the relevant source line
- If any tests fail, diagnose the root cause before suggesting a fix:
- Is it a logic error in the implementation?
- Is it a test that needs updating due to an intentional behavior change?
- Is it a missing edge case?
- Do NOT suggest disabling or skipping tests to make the suite pass.
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 · 15 lines · 0 tokens per session scan A 737c346e7e7c
test is a command published in the GitHub repository sandeep-alluru/groundcrew (0 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 157 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-08-31.
Other commands, from other repositories
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
run
显式启动一次隔离的 Windows Computer Use 任务.
doctor
检查 Computer Use 插件、环境和 Reasonix 能力映射.
axstream-stats
Benchmark a macro and show the speed story (p50/p95 per op).
oracle-infogenius
Generate AI Architect-grade Oracle Cloud architecture visuals.
oci-diagram
Generate a professional OCI architecture diagram.