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/liam-hq/liam/test-integrationgit clone --depth 1 https://github.com/liam-hq/liamWhat 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.00007 | $0.00267 |
| Opus 5 | $0.00003 | $0.00133 |
| Sonnet 5 | $0.00001 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
test-integration 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 2d 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.
What it actually says
Task
Run integration tests in the frontend/internal-packages/agent package.
Execution:
Changes to frontend/internal-packages/agent directory and runs tests in the background:
- With arguments:
pnpm test:integration [arguments] - Without arguments:
pnpm test:integration(after confirmation)
If no arguments provided:
- Show a warning that running all integration tests will make multiple OpenAI API calls, which may take significant time and incur costs
- Ask: "Please respond with 'yes' if you'd like to proceed"
- Only execute if user confirms
If arguments provided: Execute directly without confirmation (assumes targeted test execution)
Background Execution:
- Execute the command in the background using Bash tool with
run_in_background: true - Check the output every 2 minutes using BashOutput tool
- Continue checking until the tests complete
- Report the final results to the user
Usage Examples
- Specific file:
src/pm-agent/nodes/analyzeRequirementsNode.integration.test.ts - File name:
analyzeRequirementsNode.integration.test.ts - All tests: (no arguments - requires confirmation)
Arguments
$ARGUMENTS
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.
- 2d ago First seen · 33 lines · 7 tokens per session scan A 4de428b065b7
test-integration is a command published in the GitHub repository liam-hq/liam (5,100 stars, last pushed 4d ago), licensed Apache-2.0. It adds 7 tokens to every session and 267 once invoked, about $0.0000 per session on Opus 5. 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-30.
Other commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
archive
Manually archive completed increments and sync living docs - NEVER auto-archives, explicit user action only.
github-status
Check GitHub sync status for SpecWeave increment. Shows issue number, sync state, progress, last update, and any sync issues. Useful for troubleshooting and monitoring.
cancel-auto
Command "cancel-auto" from anton-abyzov/specweave, covering cancel auto session, usage, options, examples and force cancel without confirmation.
doctor
Run installation health diagnostics - detect ghost commands, stale cache, hash mismatches, and namespace pollution. Use when saying "doctor", "health check", "diagnose installation", or "check installation".