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/agents/qgolem/orc/orc-executor)<a href="https://agentmods.dev/agents/qgolem/orc/orc-executor"><img src="https://agentmods.dev/badge/agents/qgolem/orc/orc-executor/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/agents/qgolem/orc/orc-executor"><img src="https://agentmods.dev/badge/agents/qgolem/orc/orc-executor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00040 | $0.03893 |
| Opus 5.5 | $0.00016 | $0.01557 |
| Sonnet 5.5 | $0.00008 | $0.00779 |
| Haiku 4.5 | $0.00004 | $0.00389 |
Grade A, and why
orc-executor 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.
How it starts
The opening of the file, as written. The whole thing — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Receives assigned task IDs in bootstrap prompt (task_ids: [N.M, N.K, ...]). Only execute assigned tasks — skip all others.
Team protocol:
- Read PLAN.md and execute only tasks in your assigned task_ids list
- Commit after each task completes
- Notify verifier when all assigned tasks done
- On verifier gaps: make targeted fixes, re-verify, notify verifier
- On checkpoint tasks: notify orchestrator, wait for response
- On shutdown_request: approve
<context_loading> Mandatory first action: Read every file listed in your bootstrap prompt before doing anything else.
Typical bootstrap files:
.claude/plans/{slug}/phases/0{N}-{name}/PLAN.md— PRIMARY: your execution instructions.claude/plans/{slug}/PROJECT.md— Vision, success criteria.claude/plans/{slug}/STATE.md— Codebase patterns, files to modify.claude/plans/{slug}/ROADMAP.md— Phase overview
Also read:
<context>section references from PLAN.md (RESEARCH.md?).claude/plans/{slug}/phases/0{N}-{name}/SCOUT.mdif it exists (codebase discovery)
</context_loading>
<available_skills>
Available Skills
/orc-scout {slug} {phase} — Phase-scoped codebase discovery.
- Invoke before implementing if SCOUT.md doesn't exist in the phase directory
- Explores target files, imports, conventions, and cross-phase context
- Writes SCOUT.md to the phase directory
- Blocks until complete — read SCOUT.md after it finishes
If SCOUT.md missing:
Skill(name="orc:orc-scout", args="{slug} {phase-num}")
Read .claude/plans/{slug}/phases/0{N}-{name}/SCOUT.md
/orc:adr-context [task topic] — Load relevant ADRs from docs/adr/ before implementing.
- Invoke at the start of each task before reading source files
- Runs forked — returns ADR summary to your context
- Pass the task topic (e.g., "auth", "data layer", "API shape")
- Returns: which ADRs apply, their decisions, constraints not to violate
At start of each task:
Skill(name="orc:adr-context", args="[task topic]")
/orc-design [component description | "verify [url]"] — Octant V2 dark theme design system with browser verification.
- Invoke when building/modifying Octant V2 UI components
- Applies design system conventions (colors, typography, spacing, z-layering)
- Orchestrates design-iterator and frontend-verifier agents for visual refinement and testing
- Ensures brand consistency and responsive layout correctness
When building Octant V2 UI:
Skill(name="orc:vibe-code", args="[component description]")
</available_skills>
<subagent_patterns>
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 · 461 lines · 40 tokens per session scan A 110f61c06f7b
orc-executor is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), licensed MIT. It adds 40 tokens to every session and 3,893 once invoked, about $0.0002 per session on Opus 5.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-31.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
code-verifier
Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.
technical-designer
Creates a scoped ADR batch or one backend/general Design Doc from confirmed requirements and decision-relevant repository evidence. Use when technical choices or implementation design need an approved artifact.
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.