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/azrtydxb/procoder/lintgit clone --depth 1 https://github.com/azrtydxb/procoderWhat 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.00021 | $0.00389 |
| Opus 5 | $0.00010 | $0.00195 |
| Sonnet 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 2d 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.
- 2d ago First seen · 30 lines · 21 tokens per session scan A f618a26e8738
lint is a command published in the GitHub repository azrtydxb/procoder (196 stars, last pushed 2d ago), licensed Apache-2.0. It adds 21 tokens to every session and 389 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-30.
Other commands, from other repositories
setup
Initialize a new project with SDLC-compliant structure. Creates required files, configures build system, sets up CI/CD, and establishes quality tooling.
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.
run-tests
Run automated functional tests using the hook-driven test framework. Execute the test suite to validate all project functionality.
test-report
Generate test execution report in markdown format.
add-test
Interactively add a new test definition to the test suite.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.