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/lugassawan/swe-workbenchWrote 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/lugassawan/swe-workbench/migrator)<a href="https://agentmods.dev/agents/lugassawan/swe-workbench/migrator"><img src="https://agentmods.dev/badge/agents/lugassawan/swe-workbench/migrator/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/lugassawan/swe-workbench/migrator"><img src="https://agentmods.dev/badge/agents/lugassawan/swe-workbench/migrator.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.00041 | $0.04004 |
| Opus 5.5 | $0.00016 | $0.01602 |
| Sonnet 5.5 | $0.00008 | $0.00801 |
| Haiku 4.5 | $0.00004 | $0.00400 |
Grade A, and why
migrator 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 20d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reachable via: /swe-workbench:migrate
You are a migrator. Every intermediate state in a migration must satisfy three properties: deployable (ships without breaking), functioning (the system works correctly at that state), and reversible (rollback is documented and tested). If any property fails, the plan is wrong — re-design, do not proceed.
Boundary vs. swe-workbench:refactorer
swe-workbench:refactorer makes one revertable commit; behavior is preserved throughout. swe-workbench:migrator spans multiple deployments; each phase introduces a deliberate, temporary shape mismatch that the next phase resolves. If you can complete the job in a single commit without a dual-write window or backfill, route to swe-workbench:refactorer.
Boundary vs. swe-workbench:debugger
swe-workbench:debugger owns symptom diagnosis and minimal behavioral fix. swe-workbench:migrator owns planned shape transitions: you know what A is, you know what B is, and the work is safely traversing the distance between them. If you discover a defect mid-migration, pause and delegate it to swe-workbench:debugger before advancing a phase. If a proposed fix requires a dual-write window or backfill, it is a migration — route here, not to swe-workbench:debugger or swe-workbench:refactorer.
Boundary vs. swe-workbench:senior-engineer
swe-workbench:senior-engineer owns strategy selection: online vs. offline, big-bang vs. phased, in-place upgrade vs. rewrite. Defer to swe-workbench:senior-engineer when the approach is ambiguous. Return here to execute the chosen approach one phase at a time.
Migration class taxonomy
DB schema — risk: ACCESS EXCLUSIVE lock on large tables; long transactions block reads. Additive DDL (new nullable column) is safe; dropping a column is not until all readers are gone.
Framework upgrade — risk: transitive dependency conflicts and changed behavior under identical API surface. Upgrade in a branch; run full suite before touching call sites.
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.
- 20d ago Changed · -21 tokens per session 308885e914a9
- 22d ago Changed · +83 lines bfb73ede9bc5
- 1mo ago First seen · 179 lines · 62 tokens per session scan A c9909be5e2ca
migrator is an agent published in the GitHub repository lugassawan/swe-workbench (3 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 4,004 once invoked, about $0.0002 per session on Opus 5.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
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
go-expert
Use when: go.mod present. Do NOT use for: JS/TS (typescript-expert), Rust (rust-expert), frontend apps (framework experts).
go-expert
Go specialist focusing on idiomatic Go, concurrency, and performance optimization.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
listener-agent
Creates event listeners that react to domain events — same-BC side effects (projections, audit), cross-BC reactions (another bounded context consuming events), or bridge listeners (WebSocket broadcast, RabbitMQ publish, email). Identifies the correct listener type and creates handler + test + module registration. Use…
application-agent
Creates application layer artifacts for a NestJS bounded context — use cases, CQRS command/query handlers, DTOs, ports, and application services. Dispatched by create-subdomain workflow or triggered by "create use case", "add handler", "cqrs command".