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.
npx agentmods add agents/arch1esun/arcgentic/orchestratorgit clone --depth 1 https://github.com/Arch1eSUN/ArcgenticWrote 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/arch1esun/arcgentic/orchestrator)<a href="https://agentmods.dev/agents/arch1esun/arcgentic/orchestrator"><img src="https://agentmods.dev/badge/agents/arch1esun/arcgentic/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 | $0.00105 | $0.01074 |
| Opus 5 | $0.00053 | $0.00537 |
| Sonnet 5 | $0.00021 | $0.00215 |
| Haiku 4.5 | $0.00011 | $0.00107 |
Grade A, and why
arcgentic-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 5d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
arcgentic orchestrator sub-agent
Use case
The main Claude session can either:
- Load
arcgentic:orchestrate-roundskill and BE the orchestrator (Mode A — single-session) - Dispatch this orchestrator agent and let IT BE the orchestrator (delegated single-session)
This agent is the dispatched form. Useful when the main session wants to keep its context for OTHER work while the round runs.
Inherited context
- Plugin install path
- Project root
- State file path
- Current round id (or "create new round")
Procedure
LOOP until current state is terminal (closed) OR blocked:
1. Read state.yaml
2. Run scripts/state/pickup.sh — get role + action for current state
3. DETERMINE action:
├─ State = intake → ask founder for scope (if founder available in this session)
├─ State = planning → dispatch planner-agent (post-MVP; for MVP: report "manual planning needed")
├─ State = awaiting_dev_start → wait for founder OR dispatch developer-agent (post-MVP)
├─ State = dev_in_progress → dispatch developer-agent (post-MVP)
├─ State = awaiting_audit → dispatch arcgentic-auditor agent (MVP-supported)
├─ State = audit_in_progress → wait for auditor (it's running)
├─ State = passed → dispatch lesson-codifier agent (post-MVP) OR apply protocol inline
├─ State = needs_fix → report to founder; cannot proceed without founder fix-trigger
├─ State = fix_in_progress → dispatch developer-agent for fix (post-MVP)
└─ State = closed → return "DONE — round <id> closed"
4. EXECUTE action → wait for sub-agent result
5. VERIFY sub-agent output (5-step verification from sub-agent-dispatch.md)
6. CALL transition.sh with appropriate gate
7. If transition refused → diagnose, attempt 1 fix, OR escalate
END LOOP
RETURN status:
- "DONE — round closed at <verdict-commit>, outcome <PASS|NEEDS_FIX>"
- "BLOCKED — <state>, reason: <description>"
- "STUCK — <state>, manual intervention required: <action>"
Sub-agent dispatch (MVP)
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.
- 5d ago First seen · 97 lines · 105 tokens per session scan A 779a59d0bbcd
arcgentic-orchestrator is an agent published in the GitHub repository Arch1eSUN/Arcgentic (292 stars, last pushed 23d ago), licensed MIT. It adds 105 tokens to every session and 1,074 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-30.
Other agents, from other repositories
triage-labels
Label vocabulary for triaging/grilling issues in this repository. Managed by smallhours setup — edit .smallhours.yml labels: to rename, then re-run setup; do not edit this file by hand.
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
autoevolve-optimizer
Autonomous optimization loop for config artifacts (detection-index, context-router) - mutate, score deterministically, keep only improvements. Two code-enforced safety gates wrap the loop.
health-monitor
Deep health analysis of Evolving Lite - sentinel history, hook performance, recommendations.
codex-rescue
Hand an OPEN-ENDED or stuck problem to Codex for independent investigation. Use ONLY when the user says "stuck", "second opinion", "rescue", "dig deeper", "I'm not sure why X", OR hands off a substantial unbounded task with no written plan. Do NOT use when a plan or plan-step file is in context (use codex-execute) or…