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/azrtydxb/procoderWrote 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/azrtydxb/procoder/lint)<a href="https://agentmods.dev/commands/azrtydxb/procoder/lint"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/lint/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/azrtydxb/procoder/lint"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/lint.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.00021 | $0.00389 |
| Opus 5.5 | $0.00008 | $0.00156 |
| Sonnet 5.5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
lint 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
The user invoked /procoder:lint with arguments: $ARGUMENTS
The command below is the procoder binary on PATH.
- Run
procoder lint(orprocoder lint <paths>with arguments). Each finding isfile:line message (lint)from the ecosystem's canonical linter — golangci-lint, ruff check, shellcheck, eslint — under the project's own configuration. - Judge every finding honestly: fix what is real, and say why for anything you leave (a false positive, a deliberate choice). Never silence a finding by deleting the code's intent.
- Lines saying NOT checked mean a linter is missing — run
procoder init. Configless plain JavaScript gets the procoder baseline (eslint's built-in core rules, labeled "procoder baseline") — the project's own config always wins when present. Configless TypeScript stays out of scope: its parser is not built into eslint, and procoder installs no packages into repos. - Findings are informational by default; the repo can make them block the
gate with
[lint] policy = "block"in .procoder/config.toml. procoder lint --types [paths]adds the type-checker where the linter does not compile the code:tsc --noEmitfor TypeScript (under the project's own tsconfig) and pyright for Python. Go and Rust need no flag — their linters already compile. Use it after refactors and renames to catch type fallout the linters cannot see.- Re-run after fixing and show the user the result.
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 · 30 lines · 21 tokens per session scan A f618a26e8738
lint is a command published in the GitHub repository azrtydxb/procoder (211 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 389 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-30.
Other commands, from other repositories
logic-fix-all
Autonomous audit-and-fix — after consent, scan the target, fix every logic issue found (all severities), verify each fix, and report anything unresolved.
logic-explain
Trace execution step by step — use when code behavior is surprising or confusing.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
logic-locate
Locate the root cause of a confirmed failure — use when you have a stack trace, failing test, or wrong output.
logic-review
Review code for logic bugs — use when you suspect something is wrong but have no failing test yet.
verify
Verify code, architecture, or bug fixes using Chain-of-Verification.