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/logi-cmd/agent-guardrails/fixgit clone --depth 1 https://github.com/logi-cmd/agent-guardrailsWhat 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.00010 | $0.00324 |
| Opus 5 | $0.00005 | $0.00162 |
| Sonnet 5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
fix 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
/ag:fix - Auto-Fix
Triggers
- Guardrail check found issues
- User wants to fix safe issues automatically
- User types
/ag:fix
Context Trigger Pattern
/ag:fix [--dry-run]
Default behavior: Apply Tier-1 auto-fixes (safe, reversible)
Behavioral Flow
- Scan: Run guardrail check to identify fixable issues
- Filter: Only Tier-1 fixes (safe, reversible)
- Preview: Show what will be fixed
- Apply: Execute fixes with rollback capability
- Verify: Re-check after fixes applied
Fixable Issues (Tier 1)
- ✅ Missing evidence file → Create it
- ✅ Missing test stub → Create stub
- ✅ .gitignore not updated → Add entries
- ✅ Empty evidence sections → Populate templates
Examples
Auto-fix
/ag:fix
# Scans for Tier-1 issues and applies fixes
Dry run
/ag:fix --dry-run
# Shows what would be fixed without applying
Boundaries
Will:
- Fix safe, reversible issues
- Show preview before applying
- Rollback if fix fails
Will Not:
- Fix business logic issues
- Modify source code
- Override user-specified constraints
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 · 60 lines · 10 tokens per session scan A 08467151c038
fix is a command published in the GitHub repository logi-cmd/agent-guardrails (29 stars, last pushed 17d ago), licensed MIT. It adds 10 tokens to every session and 324 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
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
build
Run full verification pipeline.
doctor
Run IJFW health check (files, MCP server, hooks, memory, caps, framing).
release
Walk the llmwiki release process step by step.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
capture-feedback
Quick feedback capture with structured signals.