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/qGolem/orcWrote 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/qgolem/orc/orc)<a href="https://agentmods.dev/plugins/qgolem/orc/orc"><img src="https://agentmods.dev/badge/plugins/qgolem/orc/orc/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/qgolem/orc/orc"><img src="https://agentmods.dev/badge/plugins/qgolem/orc/orc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
orc 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
{
"name": "orc",
"version": "0.1.0",
"description": "Orchestrated planning, code review, and developer workflow skills",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 28 skills, 27 agents travel with it, and installing the plugin installs all of them — 1,775 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill map A 16 tokens
- Skill prototype A 12 tokens
- Skill compound-diagram A 18 tokens
- Skill document A 9 tokens
- Skill orc-discuss A 8 tokens
- Skill zed A 16 tokens
- Skill adr A 9 tokens
- Skill audit A 22 tokens
- Skill compound-md A 13 tokens
- Skill compound-memory A 9 tokens
- Skill orc-generate A 17 tokens
- Skill swarm A 9 tokens
- Skill diagram A 8 tokens
- Skill review A 9 tokens
- Skill orc-clarify A 15 tokens
- Skill vibe-code A 15 tokens
- Skill design-system A 13 tokens
- Skill orc-scout A 12 tokens
- Skill zed-conversation A 10 tokens
- Skill adr-context A 14 tokens
- Skill orc-discover A 17 tokens
- Skill arch B 24 tokens
- Skill orc-research B 12 tokens
- Skill phase-research B 20 tokens
- Skill half-clone B 10 tokens
- Skill install C 25 tokens
- Skill compound-pr C 17 tokens
- Skill stress-test C 11 tokens
- Agent design-iterator A 55 tokens
- Agent orc-impl-verifier A 33 tokens
- Agent orc-plan-checker A 25 tokens
- Agent orc-planner A 21 tokens
- Agent orc-executor A 40 tokens
- Agent code-reviewer A 58 tokens
- Agent drawio A 46 tokens
- Agent orc-project-researcher A 35 tokens
- Agent figma-design-sync A 57 tokens
- Agent frontend-verifier A 59 tokens
- Agent orc-research-synthesizer A 35 tokens
- Agent repo-research-analyst A 55 tokens
- Agent security-reviewer A 83 tokens
- Agent codemap-generator A 62 tokens
- Agent type-design-analyzer A 59 tokens
- Agent orc-adr-sentinel A 33 tokens
- Agent deployment-engineer A 40 tokens
- Agent performance-engineer A 40 tokens
- Agent silent-failure-hunter A 69 tokens
- Agent spec-flow-analyzer A 66 tokens
- Agent test-analyzer A 74 tokens
- Agent git-history-analyzer A 60 tokens
- Agent audit-orchestrator A 55 tokens
- Agent orc-phase-researcher B 39 tokens
- Agent orc-codebase-mapper C 45 tokens
- Agent build-error-resolver C 71 tokens
- Agent pattern-recognition-specialist A 70 tokens
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 · 7 lines scan A 90b9a9200987
orc is a plugin published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), 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
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).
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).
slopmop marketplace
Slop-mop quality gates as a Claude skill — directed remediation for AI-assisted codebases.
slopmop
Quality gates for AI-assisted codebases — catch the slop LLMs leave behind. Provides refit onboarding, the swab/scour/buff/sail remediation loop, and barnacle friction reporting as a Claude skill and slash commands.
cursor
Local Cursor Agent CLI delegation: multi family consults, Composer implementation in owned worktrees, review, resumable history, background jobs, and setup health checks.
archlint
Catches architectural drift while the agent writes code — checks edited files' imports against layer rules declared in your CLAUDE.md.