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/statusgit 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.00009 | $0.00275 |
| Opus 5 | $0.00005 | $0.00138 |
| Sonnet 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 3d 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.
- 3d 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 (29 stars, last pushed 17d ago), licensed MIT. It adds 9 tokens to every session and 275 once invoked, about $0.0000 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.