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/plugins/azrtydxb/procoder/gemini-extension)<a href="https://agentmods.dev/plugins/azrtydxb/procoder/gemini-extension"><img src="https://agentmods.dev/badge/plugins/azrtydxb/procoder/gemini-extension/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/plugins/azrtydxb/procoder/gemini-extension"><img src="https://agentmods.dev/badge/plugins/azrtydxb/procoder/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
procoder 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
{
"name": "procoder",
"version": "3.5.0",
"description": "A harness that gives AI coders the tools and skills to work like a senior developer",
"contextFileName": "AGENTS.md"
}
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 · 7 lines scan A 37119a3c486a
procoder is a plugin published in the GitHub repository azrtydxb/procoder (202 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-07.
Other plugins, from other repositories
x-dev-pipeline
Structured dev workflow with spec, user-global risk RAG, task breakdown, execution, verify, qa-gate, fix loops, and audits.
hi-vibe
Vibe-coding seatbelt for Claude Code — doc automation (CLAUDE.md/MODULE.md/handover/CHANGELOG) + AI discipline (root-cause first, no unfounded claims) + machine enforcement (ruff/eslint/import cycles).
fable-discipline
Fable's engineering discipline for any Claude session, with one habit enforced by a hook. Two layers: running the task (stage, verify each stage with a failable check, written done-criteria) and writing the code (recon before edit, verify against a copy with a negative self-test, single-writer chokepoints…
orc
Orchestrated planning, code review, and developer workflow skills.
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
argot
A guardrail that flags code foreign to a repo's own patterns — learned from git history. Bundles the argot-setup, argot-refresh, argot-check, argot-review-pr, argot-setup-ci, argot-write-rule, and argot-suggest-rules skills, the argot MCP server, and an opt-in, non-blocking pre-write guardrail hook.