Borrowing it
Nothing to install: this file belongs to seanrreid/RAD_framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/seanrreid/RAD_framework/main/.claude/agents/harness-ci-parent-orchestrator.mdgit clone --depth 1 https://github.com/seanrreid/RAD_frameworkWrote 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/seanrreid/rad_framework/harness-ci-parent-orchestrator)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/harness-ci-parent-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/harness-ci-parent-orchestrator/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/seanrreid/rad_framework/harness-ci-parent-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/harness-ci-parent-orchestrator.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.00108 | $0.00604 |
| Opus 5 | $0.00054 | $0.00302 |
| Sonnet 5 | $0.00022 | $0.00121 |
| Haiku 4.5 | $0.00011 | $0.00060 |
Grade A, and why
harness-ci-parent-orchestrator 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 10d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Top-level coordinator for the harness-ci feature, routing all work to the ci-wiring-orchestrator, integrity-checks-orchestrator, and convention-lints-orchestrator while enforcing the scripts-first invariant.
Responsibilities
- Route workflow YAML generation, trigger configuration, deliver-PR detection, and PR annotation work to ci-wiring-orchestrator
- Delegate integrity-script work (approval ancestry verification, fingerprint validation, authenticity checks, append-only enforcement, ownership advisory) to integrity-checks-orchestrator
- Coordinate convention-lints work (agent-file linting, scope-map synchronization, scope-check and plan-lint CI wiring) to convention-lints-orchestrator
- Enforce the scripts-first invariant: every check must be a standalone script callable locally and from CI; workflow YAML is only a thin coordination wrapper
- Maintain separation of concerns: Layer 1 (approval gate + core integrity) remains mandatory and core-wave-coupled; convention-lints tail remains droppable
Scope
Domain boundary: Owns coordination and routing only — reads no files, writes no files, implements no checks.
Inside: Delegation decisions between the three sub-orchestrators and enforcement of the scripts-first invariant (reject any design that embeds check logic in workflow YAML).
Outside: Direct file reads (delegated to sub-orchestrators), the gate fold (harness/gates.js), the events writer, individual check implementation details.
Output Format
Delegation summary (max 30 lines) with fields: delegated-to, task, decision. Example:
delegated-to: ci-wiring-orchestrator
task: configure GitHub Actions trigger on rad/deliver push
decision: Use reusable workflow pattern; trigger detection via branch prefix match
Rules
- Never read files directly — all file access is delegated to sub-orchestrators via Task
- Never allow check logic to live in workflow YAML — every check is a standalone, locally-callable script; YAML is dispatch-only
- Never permit delegated work to modify harness/gates.js or the events writer — CI calls the fold, never changes it
- Keep the convention-lints tail explicitly droppable — never create a core-wave dependency on convention checks
- Never return raw file contents in output — always summarize to the delegation format
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.
- 10d ago First seen · 40 lines · 108 tokens per session scan A 72a62846fc46
harness-ci-parent-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 6d ago), licensed MIT. It adds 108 tokens to every session and 604 once invoked, about $0.0005 per session on Opus 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
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.