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/implement-regression-testsgit 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.00012 | $0.00243 |
| Opus 5 | $0.00006 | $0.00121 |
| Sonnet 5 | $0.00002 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
implement-regression-tests 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
Implement Regression Tests Command
Implement tests marked with it.skip. Test current behavior as it exists today.
Arguments: $ARGUMENTS
Task
- Find
it.skiptests in the specified file/directory - Change
it.skiptoit - Implement test body based on CURRENT behavior
- Run tests to verify they pass
Critical Rules
- Test CURRENT behavior - Not ideal behavior
- Tests MUST pass - They document what IS
- Follow test principles - See @docs/test-principles.md
- Minimal mocking - Only at external boundaries
Example
// Before (it.skip)
it.skip("returns null when user not found (current behavior)", () => {
// TODO: Implement test
});
// After (implemented)
it("returns null when user not found (current behavior)", () => {
const result = getUserById("non-existent-id");
expect(result).toBeNull();
});
Remember: These are regression tests - they protect existing behavior from breaking.
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 · 42 lines · 12 tokens per session scan A 385a067769ce
implement-regression-tests is a command published in the GitHub repository liam-hq/liam (5,100 stars, last pushed 4d ago), licensed Apache-2.0. It adds 12 tokens to every session and 243 once invoked, about $0.0001 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.
github-push
Push local progress to GitHub Issues (like git push). Updates issue with task completion checklist.
export
Export the wiki (or architecture model) to markdown, HTML, JSON, or Structurizr DSL.
review-teardown
Delete a review branch to free the shared Pantheon review slot.
docguard.guard
Run DocGuard guard validation — check all validators and fix any issues.