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.
git clone --depth 1 https://github.com/logi-cmd/agent-guardrailsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/logi-cmd/agent-guardrails/fix)<a href="https://agentmods.dev/commands/logi-cmd/agent-guardrails/fix"><img src="https://agentmods.dev/badge/commands/logi-cmd/agent-guardrails/fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/logi-cmd/agent-guardrails/fix"><img src="https://agentmods.dev/badge/commands/logi-cmd/agent-guardrails/fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00010 | $0.00324 |
| Opus 5.5 | $0.00004 | $0.00130 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (27 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 324 once invoked, about $0.0000 per session on Opus 5.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
performance-optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
lint-check
Runs linting and code quality checks. Catches style issues, potential bugs, and enforces project standards.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
doctor
Check md-anything capabilities and available optional tools.