al

al is a command for coding agents from 0xmariowu/AgentLint. It costs 30 tokens per session (6,332 once invoked), scanned A, original, MIT.

A command that runs AgentLint diagnostics across projects. AgentLint checks whether an AI-friendly repository is findable, well-instructed, workable, continuous between sessions, safe, and properly harnessed.

In plain words
What is it for?
Use it to inspect project instructions, tests, hooks, permissions, secrets, CI setup, and handoff readiness, with deeper or session-log analysis when selected.
Why use it?
It brings several repository checks into one guided command instead of requiring separate inspections. Optional analyses can also look for contradictions or issues in session logs.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the agent-lint plugin — 2 commands, 1 agent, 1 hook shipped together

Install

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.

agentmods
npx agentmods add commands/0xmariowu/agentlint/al
Clone the repo
git clone --depth 1 https://github.com/0xmariowu/AgentLint

Or install agent-lint, the plugin that ships this one along with the rest of its 2 commands, 1 agent, 1 hook.

Wrote 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.

agentmods badge for al

README.md
[![agentmods](https://agentmods.dev/badge/commands/0xmariowu/agentlint/al.svg)](https://agentmods.dev/commands/0xmariowu/agentlint/al)
Your own site
<a href="https://agentmods.dev/commands/0xmariowu/agentlint/al"><img src="https://agentmods.dev/badge/commands/0xmariowu/agentlint/al.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,332 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.06332
Opus 5 $0.00015 $0.03166
Sonnet 5 $0.00006 $0.01266
Haiku 4.5 $0.00003 $0.00633

Measured 5d ago against content hash ba1b4a141561, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

al 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 5d 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.

commands/al.md · 607 lines

How it starts

The opening of the file, as written. The whole thing — 607 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/al — AgentLint

Diagnose, plan, fix. One command. User presses Enter twice at most.

Flow

Step 1: Module Selection

AskUserQuestion with defaults pre-selected (user can press Enter to accept):

AgentLint — which checks to run?

Core (deterministic, no AI calls) — default ON:
  ☑ Findability         — can AI find what it needs?
  ☑ Instruction Quality — are your rules well-written?
  ☑ Workability         — can AI build and test?
  ☑ Continuity          — can next session pick up?
  ☑ Safety              — are secrets and CI locked down?
  ☑ Harness             — are Claude Code hooks/permissions safe?

Extended (opt-in, runtime-dependent):
  ☐ Deep Analysis       — find contradictions, dead weight, vague rules (uses AI)
  ☐ Session Analysis    — discover issues from your Claude Code session logs

[Enter to run with defaults]

Default: all 6 core dimensions. Extended analyzers are optional and will show as n/a in the output unless explicitly checked. User presses Enter → runs immediately.

Record the normalized choices in shell variables for the config write in Step 2. Core is currently all-or-nothing and defaults on; Deep/Session are the only runtime-selectable modules.

RUN_CORE=true
RUN_DEEP=false     # set true only if Deep Analysis was selected
RUN_SESSION=false  # set true only if Session Analysis was selected

Step 2: Init (first run only)

If ${CLAUDE_PLUGIN_DATA}/config.json doesn't exist, ask with default:

Where are your projects? [~/Projects]: ↵

Press Enter → uses ~/Projects. Save to ${CLAUDE_PLUGIN_DATA}/config.json. Never ask for the projects root again.

After Step 1, always persist the selected scan options back into the same config file. The scan and verify steps must read this file instead of relying on stale shell variables; otherwise the config is dead state and Deep/Session choices are ignored.

CONFIG_DIR="${CLAUDE_PLUGIN_DATA:-$HOME/.al}"
CONFIG_FILE="$CONFIG_DIR/config.json"
mkdir -p "$CONFIG_DIR"

if [ ! -f "$CONFIG_FILE" ]; then
  PROJECTS_ROOT_INPUT="${PROJECTS_ROOT_INPUT:-$HOME/Projects}"
  node -e '
    const fs = require("fs");
    const file = process.argv[1];
    const projectsRoot = process.argv[2];
    fs.writeFileSync(file, JSON.stringify({
      projects_root: projectsRoot,
      modules: { core: true, deep: false, session: false }
    }, null, 2) + "\n");
  ' "$CONFIG_FILE" "$PROJECTS_ROOT_INPUT"
fi

CONFIG_TMP="$(mktemp "$CONFIG_DIR/config.XXXXXX")"
node -e '
  const fs = require("fs");
  const [file, out, core, deep, session] = process.argv.slice(1);
  const cfg = JSON.parse(fs.readFileSync(file, "utf8"));
  cfg.modules = {
    ...(cfg.modules || {}),
    core: core === "true",
    deep: deep === "true",
    session: session === "true"
  };
  fs.writeFileSync(out, JSON.stringify(cfg, null, 2) + "\n");
' "$CONFIG_FILE" "$CONFIG_TMP" "$RUN_CORE" "$RUN_DEEP" "$RUN_SESSION"
mv "$CONFIG_TMP" "$CONFIG_FILE"

Read the full file on GitHub · 607 lines

Changes

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.

  1. 5d ago First seen · 607 lines · 30 tokens per session scan A ba1b4a141561

Subscribe to this mod's changes

al is a command published in the GitHub repository 0xmariowu/AgentLint (55 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 6,332 once invoked, about $0.0002 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.