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/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/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/mauhpr/agentlint-plugin/lint-status"><img src="https://agentmods.dev/badge/commands/mauhpr/agentlint-plugin/lint-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.00015 | $0.00187 |
| Opus 5.5 | $0.00006 | $0.00075 |
| Sonnet 5.5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00019 |
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 15d 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 summarize:
- Coverage: for Claude, whether hooks are configured, and when AgentLint last observed a hook call (if "never observed", say so plainly).
- Effective policy: policy files in effect (workspace / repository), active packs, rule count, severity mode, required rules, and any pack drift warnings.
- AgentChute (optional cloud): off, healthy or degraded, and what is still enforced locally.
- Session activity and findings this session, if reported.
Use agentlint status --json if you need exact fields. If anything looks wrong,
suggest agentlint doctor --project-dir "$CLAUDE_PROJECT_DIR" (read-only;
--fix repairs).
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.
- 15d ago Changed · +4 lines · +1 tokens per session 43d4339bf157
- 1mo 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 3d ago), licensed MIT. It adds 15 tokens to every session and 187 once invoked, about $0.0001 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-31.
Other commands, from other repositories
repair
A repair-and-check loop for Phase 1a work. It runs only after sodam-loop-start has enabled the loop.
unstuck
USE WHEN stuck on a bug, architecture decision, or recurring failure. Applies 5 perspectives sequentially (Researcher → Architect → Contrarian → Simplifier → Hacker) to break deadlock.
step3-execute-slice
Pipeline Step 3 — Execute a hardened plan slice-by-slice with validation gates, re-anchoring, and rollback protocol.
build-fix
Systematically investigate and fix build errors, TypeScript errors, or test failures with minimal diffs.
data-flow-analysis
Trace how data flows through the system from input to output.
doctor
Check the Modellix CLI install, credential resolution, API connectivity, and balance.