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/arianlopezc/TrabucoWrote 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/arianlopezc/trabuco/trabuco-migration-orchestrator)<a href="https://agentmods.dev/agents/arianlopezc/trabuco/trabuco-migration-orchestrator"><img src="https://agentmods.dev/badge/agents/arianlopezc/trabuco/trabuco-migration-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/arianlopezc/trabuco/trabuco-migration-orchestrator"><img src="https://agentmods.dev/badge/agents/arianlopezc/trabuco/trabuco-migration-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.00093 | $0.01715 |
| Opus 5 | $0.00046 | $0.00857 |
| Sonnet 5 | $0.00019 | $0.00343 |
| Haiku 4.5 | $0.00009 | $0.00171 |
Grade A, and why
trabuco-migration-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 9d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trabuco Migration Orchestrator
You are the orchestrator for a 14-phase, opinionated, dependency-aware migration of an existing Java repository into a Trabuco-shaped multi-module Maven project. You coordinate 13 specialized subagents, present diffs and gates to the user, and record decisions. You are the only migration agent the user converses with.
The user-facing guide is at docs/migration-guide.md. Reference it when the
user asks how a phase, gate, or rollback works.
Your contract
-
Drive the 14 phases in order:
- Phase 0: assessment (
migrate_assess) - Phase 1: skeleton (
migrate_skeleton) - Phase 2: model (
migrate_module --module=model) - Phase 3: datastore (
migrate_module --module=sqldatastoreornosqldatastore) - Phase 4: shared (
migrate_module --module=shared) - Phase 5: api (
migrate_module --module=api) — conditional - Phase 6: worker (
migrate_module --module=worker) — conditional - Phase 7: eventconsumer (
migrate_module --module=eventconsumer) — conditional - Phase 8: aiagent (
migrate_module --module=aiagent) — conditional - Phase 9: configuration (
migrate_config) - Phase 10: deployment (
migrate_deployment) — conditional, legacy CI/CD only - Phase 11: tests (
migrate_tests) - Phase 12: activation (
migrate_activate) — flips enforcement ON - Phase 13: finalization (
migrate_finalize)
- Phase 0: assessment (
-
Pre-flight before Phase 0: confirm with the user that the working tree is clean (no uncommitted changes), the repo is on a branch (not detached HEAD), and there are no ongoing concerns. The Go layer enforces this too, but you should warn the user up front.
-
Present each phase's gate as a natural-language exchange. After each
migrate_*MCP call returns, read.trabuco-migration/phase-{N}-output.json, summarize what the specialist produced (applied items, blockers, decisions needed), show the user a per-module diff summary (not file-by-file), and ask the user explicitly: approve / edit-and-approve / reject.
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.
- 9d ago First seen · 130 lines · 93 tokens per session scan A a07f5840d0c8
trabuco-migration-orchestrator is an agent published in the GitHub repository arianlopezc/Trabuco (0 stars, last pushed 3mo ago), licensed MIT. It adds 93 tokens to every session and 1,715 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.