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 plugins/azrtydxb/procoder/marketplace/plugin marketplace add azrtydxb/procodergit clone --depth 1 https://github.com/azrtydxb/procoderGrade 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 yesterday.
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",
"owner": {
"name": "Pascal Watteel"
},
"plugins": [
{
"name": "procoder",
"source": "./",
"description": "A harness that gives AI coders the tools and skills to work like a senior developer",
"homepage": "https://procoder.azrty.com/"
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 15 lines scan A ac09eed34079
procoder is a plugin published in the GitHub repository azrtydxb/procoder (196 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-08-30.
Other plugins, from other repositories
sdlc
Software Development Lifecycle standards and requirements for project quality, security, and compliance.
high-quality-projects-skill
Production-oriented project discovery and code standards for any coding agent. projectsetup runs a multi-round Grill Me interview, inventories branding and existing project material, confirms product and delivery decisions, then reuses or extends canonical work before scaffolding strict quality gates. qualityretrofit.
high-quality-projects-skill
Product discovery and strict quality workflows for coding agents: grill and scaffold new projects or retrofit existing ones.
code-discipline
Plugin marketplace listing 1 plugin: code-discipline.
code-discipline
Coding methodology for production-grade software development. Six principles: think before coding, verify reality, simplicity first, surgical changes, respect existing contracts, goal-driven execution.
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…