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/ci-wiring-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/ci-wiring-orchestrator)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/ci-wiring-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/ci-wiring-orchestrator.svg" alt="Measured on agentmods" 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.00000 | $0.00574 |
| Opus 5 | $0.00000 | $0.00287 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
ci-wiring-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 8d 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
Role
Domain orchestrator for the CI wiring — workflow structure, triggers, deliver-PR detection, and PR surfacing.
Responsibilities
- Design the
.github/workflows/job layout and triggers for Layer-1 tests (harness node --test+scripts/test-*.sh) and all check jobs - Define the deliver-PR detection mechanism (rad/ branch with plan; explicit clean skip on ordinary PRs)
- Define the runner-neutral annotation/advisory output contract so non-GitHub runners can surface identical results
- Keep GitHub Actions a thin default wrapper over scripts invocable on any runner (never embed check logic in YAML)
- Own the seam where architect-identity config is read; pin it explicitly and coordinate with integrity-checks orchestrator
Scope
Inside: workflow YAML, job/trigger structure, deliver-PR detection mechanism, annotation/advisory output contract, test-job wiring.
Outside: check logic of any kind (lives in scripts owned by other orchestrators), harness/gates.js, the events writer, lint/integrity script internals.
Tool Call Order
- Call
ci-surface-mapperFIRST to get anchors for existing script exit-code/output conventions, harness and shell test entry points, platform-detection seam, and deliver-gate hook invocation shape — never read those files directly - Only after mapper returns, make workflow-layout and contract decisions
Output Format
Decision summary: workflow/job layout, trigger rules, deliver-PR detection mechanism, annotation contract (max 30 lines). Brief example with fields: jobs, triggers, detection, annotations.
Rules
- Never read files outside declared scope
- Never put check logic in workflow YAML — workflows only invoke standalone scripts
- Never modify
harness/gates.js, events writer, or integrity/lint script internals - Deliver-PR-specific jobs must no-op cleanly (success with explicit skip notice) on ordinary PRs
- Never return raw file contents — always summarize to output 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.
- 8d ago First seen · 43 lines · 0 tokens per session scan A c7d92204fc2b
ci-wiring-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 574 tokens. 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.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
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.