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/LuisFelipeMoro/Harness-devkitWrote 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/luisfelipemoro/harness-devkit/coding-pipeline)<a href="https://agentmods.dev/plugins/luisfelipemoro/harness-devkit/coding-pipeline"><img src="https://agentmods.dev/badge/plugins/luisfelipemoro/harness-devkit/coding-pipeline/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/luisfelipemoro/harness-devkit/coding-pipeline"><img src="https://agentmods.dev/badge/plugins/luisfelipemoro/harness-devkit/coding-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
coding-pipeline 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 today.
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": "coding-pipeline",
"version": "2.8.1",
"description": "12-agent spec-first coding pipeline (Analyst \u2192 PM \u2192 Architect \u2192 PlanReviewer \u2192 ScrumMaster \u2192 Coder \u2192 QA \u2192 Reviewer \u2192 StressTester \u2192 Tuner \u2192 Verdict \u2192 DevOps)",
"author": {
"name": "Luis Moro"
},
"hooks": "./hooks/hooks.json"
}
What it installs
The manifest is a name and a version. 6 skills, 20 agents, 5 hooks travel with it, and installing the plugin installs all of them — 1,164 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill multi-agent A 107 tokens
- Skill bug-fix A 102 tokens
- Skill planning A 91 tokens
- Skill task A 87 tokens
- Skill architecture A 79 tokens
- Skill analysis A 82 tokens
- Agent coder A 36 tokens
- Agent qa A 36 tokens
- Agent reviewer A 17 tokens
- Agent architect A 33 tokens
- Agent rote-datadog A 59 tokens
- Agent rote-github A 51 tokens
- Agent stress A 16 tokens
- Agent plan-reviewer A 38 tokens
- Agent bug-investigator A 25 tokens
- Agent rote-analytics A 30 tokens
- Agent tuner A 25 tokens
- Agent verdict A 21 tokens
- Agent devops A 32 tokens
- Agent scrum-master A 24 tokens
- Agent coder-frontend A 26 tokens
- Agent pm A 17 tokens
- Agent coder-backend A 23 tokens
- Agent orchestrator A 44 tokens
- Agent analyst A 19 tokens
- Agent rote-adapter C 44 tokens
- Hook PreToolUse A not measured
- Hook PostToolUse A not measured
- Hook PreCompact A not measured
- Hook Stop A not measured
- Hook SessionStart A not measured
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.
- today Changed d6f771cc3a9c
- 22d ago Changed eb6cf4cf2538
- 25d ago Changed c8b6e3d12703
- 1mo ago Changed 5c18090f3917
- 1mo ago Changed 4bce130a328f
- 1mo ago First seen · 10 lines scan A e0e26882b0a4
coding-pipeline is a plugin published in the GitHub repository LuisFelipeMoro/Harness-devkit (13 stars, last pushed today), licensed MIT. 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-31.
Other plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.