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/platinoff/poolai/testgit clone --depth 1 https://github.com/platinoff/poolAIWhat 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.00296 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
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.
What it actually says
Test Command
Run tests for the project.
Required CI parity (matches .github/workflows/ci.yml required step; in MSYS2 bash before cargo):
export K8S_OPENAPI_ENABLED_VERSION=1.28
cargo test --lib --tests --features ml,enterprise,cloud
Steps
- Required: run the bash block above (CI parity).
- Optional: run
cargo test --all-featuresfor a fuller matrix (heavy; on Windows MSVC may hit compiler stack issues — prefer GNU toolchain fromrust-toolchain.tomlor Linux CI) - For context memory changes:
cargo test --test context_memory_integration - For enterprise audit logger changes:
cargo test --test enterprise_audit_integration --features enterprise - For enterprise monitoring changes:
cargo test --test enterprise_monitoring_integration --features enterpriseandcargo test --test enterprise_monitoring_sqlite_integration --features enterprise - For cloud mock provider changes:
cargo test --test cloud_mock_integration --features cloud,cloud-sdk -- --test-threads=1(requiresrustc >= 1.88for AWS SDK; ensure enough free disk space to build dependencies) - Report test results and any failures
- If tests fail, analyze the failures and suggest fixes
Return test summary.
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 · 24 lines · 0 tokens per session scan A 06fcbdf5c0d8
test is a command published in the GitHub repository platinoff/poolAI (4 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 296 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.