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/yezannnnn/agentGroupWrote 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/yezannnnn/agentgroup/test)<a href="https://agentmods.dev/commands/yezannnnn/agentgroup/test"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/test/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/yezannnnn/agentgroup/test"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/test.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.00000 | $0.00751 |
| Opus 5.5 | $0.00000 | $0.00300 |
| Sonnet 5.5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
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 1mo 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.
This is a copy
100% identical to test — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run tests and fix common issues
Follow these instructions from top to bottom.
Create a TODO with EXACTLY these 4 items
- Execute test suite
- Analyze results and identify issues
- Fix common problems if found
- Provide test summary
1 · Execute test suite
First, detect the project's test runner
-
Python projects:
- If
pyproject.tomlexists with[tool.poetry]: Trypoetry run pytest - If
setup.pyorrequirements.txt: Trypytestorpython -m pytest - If custom test script exists (e.g.,
run_tests.py,run_dev.py): Use that - Add common flags:
--tb=shortfor pytest
- If
-
JavaScript/TypeScript projects:
- If
package.jsonexists: Check "scripts" section for "test" command - Common:
npm test,npm run test,yarn test,pnpm test - Framework specific:
jest,vitest,mocha
- If
-
Other languages:
- Rust:
cargo test - Go:
go test ./... - Java:
mvn testorgradle test - Ruby:
bundle exec rspecorrake test - PHP:
composer testorphpunit
- Rust:
Execute the detected test command
- RUN the appropriate test command
- CAPTURE full output including any errors
- NOTE execution time and test counts
If no test runner is found: Report this to the user and ask for the correct test command.
2 · Analyze results and identify issues
Check for common issues in this order:
Language-specific issues
Python:
- Missing init.py files (import errors, tests not discovered)
- Import path problems
- Fixture issues (pytest)
- Virtual environment problems
JavaScript/TypeScript:
- Module resolution errors
- Missing dependencies in node_modules
- Jest/Vitest configuration issues
- TypeScript compilation errors
Common across languages:
- Environment variable issues (missing config)
- Database/external service connection errors
- File path problems (absolute vs relative)
- Permission issues
3 · Fix common problems if found
ONLY fix these specific issues automatically:**
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.
- 1mo ago First seen · 124 lines · 0 tokens per session scan A 82ae7e6201b2
test is a command published in the GitHub repository yezannnnn/agentGroup (150 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 751 tokens. A static security scan graded it A with 0 findings. It is 100% identical to test, differing in 0 lines, and is treated as a copy.
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.
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…
verify
Run repository verification using the verification-loop skill.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.