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/status)<a href="https://agentmods.dev/commands/logi-cmd/agent-guardrails/status"><img src="https://agentmods.dev/badge/commands/logi-cmd/agent-guardrails/status/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/status"><img src="https://agentmods.dev/badge/commands/logi-cmd/agent-guardrails/status.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.00275 |
| Opus 5.5 | $0.00004 | $0.00110 |
| Sonnet 5.5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
status 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:status - Project Status
Triggers
- User wants to see current project state
- User wants to check task contract status
- User types
/ag:status
Context Trigger Pattern
/ag:status
Behavioral Flow
- Config: Show
.agent-guardrails/config.jsonstate - Task: Show current task contract if active
- Evidence: Show evidence file status
- Daemon: Show daemon status if running
- Summary: Quick overview of project health
Output Sections
- Configuration: Preset, allowed paths, risk level
- Task Contract: Active task, scope, risk
- Evidence: Evidence file path and last update
- Daemon: Running/stopped, last check time
- Health: Overall project health status
Examples
Show status
/ag:status
# Shows comprehensive project state
Boundaries
Will:
- Show current project state
- Display task contract details
- Report daemon status
Will Not:
- Modify files
- Run checks automatically
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 · 52 lines · 9 tokens per session scan A 543ce9849313
status 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 275 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
status
Display project status, active tracks, and next actions.
prp-prd
Interactive PRD generator - problem-first, hypothesis-driven product spec with back-and-forth questioning.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-charter
Create, import, discover, approve, or skip project charter. No-arg form is an interactive wizard.
test-management
Organize, classify, and trace Katalon True Platform/TestOps test assets. Use when you need to structure test cases into folders and suites, move or reorganize cases, search and find existing assets at scale, link or unlink requirements to test cases, or produce a requirement-to-test traceability report (which…
_closing
A set of closing rules for project-management commands that change the .pm/ project-management folder. It controls the language of summaries and links shown in the final response.