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/fix-issuegit 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.00014 | $0.00193 |
| Opus 5 | $0.00007 | $0.00097 |
| Sonnet 5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
fix-issue 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
Use the gh command to fetch the GitHub issue specified in the arguments, analyze the problem, implement the necessary changes, and verify the fix is complete.
Steps
- Extract the issue number from the arguments (format:
#123or just123) - Use
gh issue view <issue-number>to fetch the issue details - Understand the problem described in the issue
- Search the codebase for relevant files related to the issue
- Implement the necessary changes to fix the issue
- Write and run tests to verify the fix
- Ensure code passes linting and type checking (use
pnpm lint) - Create a descriptive commit message following the project's commit conventions
Arguments
The command accepts an issue number (e.g., 123 or #123)
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 · 21 lines · 14 tokens per session scan A 7c702b810ef3
fix-issue is a command published in the GitHub repository liam-hq/liam (5,100 stars, last pushed 4d ago), licensed Apache-2.0. It adds 14 tokens to every session and 193 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.