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/check)<a href="https://agentmods.dev/commands/logi-cmd/agent-guardrails/check"><img src="https://agentmods.dev/badge/commands/logi-cmd/agent-guardrails/check/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/check"><img src="https://agentmods.dev/badge/commands/logi-cmd/agent-guardrails/check.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.00009 | $0.00425 |
| Opus 5.5 | $0.00004 | $0.00170 |
| Sonnet 5.5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
check 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:check - Guardrail Check
Triggers
- User wants to validate recent changes before commit
- User wants to check scope drift, test coverage, or drift detection
- User types
/ag:check
Context Trigger Pattern
/ag:check [--base-ref <ref>] [--commands-run "<cmd1>, <cmd2>"]
Default behavior: npx agent-guardrails check --base-ref HEAD~1
Behavioral Flow
- Run: Execute
npx agent-guardrails check --base-ref HEAD~1 - Analyze: Review findings (scope-drift, missing-test, new-abstraction)
- Report: Show results in chat with severity levels
- Fix: If issues found, suggest fixes or run
/ag:fix
Key Patterns
- Scope check: Verify only intended files were modified
- Test validation: Ensure tests run or are updated
- Drift detection: Flag parallel abstractions or interface changes
Examples
Basic check
/ag:check
# Runs: npx agent-guardrails check --base-ref HEAD~1
Check with commands run
/ag:check --commands-run "npm test, npm run lint"
# Runs: npx agent-guardrails check --base-ref HEAD~1 --commands-run "npm test, npm run lint"
Check specific base
/ag:check --base-ref origin/main
# Runs: npx agent-guardrails check --base-ref origin/main
Boundaries
Will:
- Run check and report findings
- Suggest fixes for found issues
- Show confidence level of the check
Will Not:
- Automatically fix issues (use
/ag:fixinstead) - Modify files without user approval
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 · 63 lines · 9 tokens per session scan A 2f1973a6bd7c
check is a command published in the GitHub repository logi-cmd/agent-guardrails (27 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 425 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).
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…