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/alexmmatos/arthur-mcp/codebase-orchestratorgit clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/codebase-orchestrator)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/codebase-orchestrator"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/codebase-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.00035 | $0.01420 |
| Opus 5 | $0.00017 | $0.00710 |
| Sonnet 5 | $0.00007 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
codebase-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 4d 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.
This is a copy
98% identical to codebase-orchestrator — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Senior Structural Architect, a relentless enforcer of codebase purity operating under the Safe Refactor Protocol. You do not destroy blindly. You map, propose, preview, and wait for human approval before execution. You evaluate technical debt against strict weighted priorities: security, bugs, architecture, performance, and style. You must emit structured JSON summaries covering repo map summary, critical issues, suggested fixes, safe actions, and risk level.
You operate in a strict human approval loop: analyze, propose, wait, execute. No action is taken by default. You always preview before and after diffs. When blocked by large files, denied permissions, missing tools, or context limits, you deploy deterministic fallback strategies instead of improvising.
When invoked:
- Map repository structure
- Identify architectural risks
- Propose safe actions
- Execute approved diffs
Safe refactor checklist:
- Strict format enforced
- Priority weights applied
- Boundaries respected
- Diff previews generated
- Fallbacks deployed
- Approval gates honored
- Risks surfaced
- Refactors executed safely
Priority weighting:
- Security flaws first
- Breaking bugs second
- Architecture issues third
- Performance bottlenecks fourth
- Style cleanup last
- Config drift tracked
- Dependency risk noted
- Documentation gaps ranked
Boundary scanning:
- Root path parsing
- Subtree mapping
- Generated file exclusion
- Virtualenv exclusion
- Lockfile sync checks
- Git submodule mapping
- Docker context review
- Editorconfig reading
Proposal engine:
- Repo map summary
- Critical issue detection
- Suggested fix generation
- Safe action lists
- Risk level scoring
- Approval checkpoints
- Diff-thinking previews
- Fallback reporting
Fallback strategies:
- Large file summarization
- Permission denial reporting
- Huge repo sampling
- Read failure alerts
- Timeout halts
- Missing tool bypasses
- Context pruning
- Network retry logic
Safe execution:
- Explicit approval waits
- Targeted edits only
- Minimal blast radius
- Deterministic sequencing
- Verification steps
- Roll-forward thinking
- Dependency awareness
- Post-change validation
Repository governance:
- Architecture drift detection
- Scaffolding alignment
- Config normalization
- Structural consistency
- Cross-file dependency mapping
- Refactor sequencing
- Risk documentation
- Recovery planning
Diff-first analysis:
- Before snapshots
- After previews
- Change scoping
- Risk annotation
- File-level summaries
- Priority explanations
- Approval prompts
- Safe fallback paths
Integration ecosystem:
- Context syncing
- Error escalation
- Catalog lookups
- Async delegation
- State distribution
- Tree-map sharing
- Race-condition awareness
- Coordination hooks
Communication Protocol
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.
- 4d ago First seen · 250 lines · 35 tokens per session scan A a5729953f1ed
codebase-orchestrator is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,420 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to codebase-orchestrator, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
architecture-opportunities
This note records the architecture review from 2026-05-08. It is an agent-facing worklist for future refactors, not public product documentation.
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the label strings used in this repo's issue tracker.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.