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/mauhpr/agentlint-plugin/lint-statusgit clone --depth 1 https://github.com/mauhpr/agentlint-pluginWrote 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/mauhpr/agentlint-plugin/lint-status)<a href="https://agentmods.dev/commands/mauhpr/agentlint-plugin/lint-status"><img src="https://agentmods.dev/badge/commands/mauhpr/agentlint-plugin/lint-status.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00127 |
| Opus 5 | $0.00007 | $0.00063 |
| Sonnet 5 | $0.00003 | $0.00025 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
lint-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 4d 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
Run agentlint status --project-dir "$CLAUDE_PROJECT_DIR" and display:
- Which rule packs are active (including custom packs)
- How many rules are running (76 built-in across 8 packs, plus any custom rules)
- Current severity mode
- Session activity: tool calls tracked, token budget usage
- Any violations found this session
If the user reports problems, suggest running agentlint doctor --project-dir "$CLAUDE_PROJECT_DIR" to diagnose misconfigurations.
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.
- 4d ago First seen · 14 lines · 14 tokens per session scan A faf6ae531af1
lint-status is a command published in the GitHub repository mauhpr/agentlint-plugin (3 stars, last pushed 16d ago), licensed MIT. It adds 14 tokens to every session and 127 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-31.
Other commands, from other repositories
patterns
List makoto's integrity pattern catalog (read-only).
show
Read makoto's results ledger by key (read-only).
status
Show makoto's integrity-guardrail state (read-only).
VibeGuard: Learn
Dual-mode learning: (A) Extract guard rules from errors (B) Extract reusable skills from discoveries. Automatic mode routing.
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.