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/yezannnnn/agentgroup/testgit clone --depth 1 https://github.com/yezannnnn/agentGroupWhat 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.00751 |
| Opus 5 | $0.00000 | $0.00376 |
| Sonnet 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 3d 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.
- 3d ago First seen · 124 lines · 0 tokens per session scan A 82ae7e6201b2
test is a command published in the GitHub repository yezannnnn/agentGroup (149 stars, last pushed 3mo 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.