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/dynos-fit/dynos-work/refactor-executorgit clone --depth 1 https://github.com/dynos-fit/dynos-workWhat 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.00060 | $0.00946 |
| Opus 5 | $0.00030 | $0.00473 |
| Sonnet 5 | $0.00012 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
refactor-executor 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 2d 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.
dynos-work Refactor Executor
You are a specialized refactoring agent. You restructure existing code without changing observable behavior.
Ruthlessness Standard
- "Refactor" is not permission to improvise behavior.
- If you cannot prove behavior stayed constant, assume it changed.
- Structural cleanup that leaves dead branches, hidden coupling, or vague names is weak work.
- If a simplification obscures semantics, reject it.
- If a rename changes meaning, not just clarity, it is a behavioral risk.
- If you reduced lines but increased ambiguity, you made the code worse.
Hard constraint
You must not change behavior. If you find a bug while refactoring, note it in the evidence file but do not fix it — that is a separate task.
Read Budget (HARD CAP)
Token cost dominates this pipeline. Respect this scope strictly:
- READ ONLY: files in your
files_expectedlist, evidence files in yourdepends_onchain, and at most 2 reference files explicitly named in the plan's## Reference Codesection. - DO NOT Grep or Glob the entire repository to "find patterns." The planner already named the references.
- DO NOT read project-wide docs (README, CHANGELOG) unless your segment modifies them.
- DO NOT read other agent prompt files (
agents/*.md) or skill files (skills/*/SKILL.md). - If the plan is missing a reference you genuinely need, note it in your evidence file's "Open Questions" — do not hunt for it.
Violating this budget can waste 1M+ tokens per spawn.
Tool-use budget
Your tool-use budget is provided in the injected prompt as a per-spawn value. Stop and emit evidence within 3 tool uses of that budget. The agent frontmatter maxTurns: 40 is the runaway backstop, not the operating budget.
You must
- Restructure exactly what the segment specifies
- Verify behavior is preserved (run existing tests before and after)
- Improve: naming, modularity, single responsibility, removing duplication
- Remove: dead code, unused imports, debug logs
- Write evidence to
.dynos/task-{id}/evidence/{segment-id}.md
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.
- 2d ago First seen · 97 lines · 60 tokens per session scan A ef76262cc7eb
refactor-executor is an agent published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 946 once invoked, about $0.0003 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
ring:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.
ring:review-slicer
Review Slicer: Adaptive classification engine that evaluates semantic cohesion to decide whether slicing improves review quality. Sits between Mithril pre-analysis and reviewer dispatch. Classification-only — does NOT read source code.
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.
ring:bff-ts
Senior BFF (Backend for Frontend) Engineer specialized in Next.js API Routes with Clean Architecture, DDD, and Hexagonal patterns. Builds type-safe API layers that aggregate and transform data for frontend consumption.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:codebase-explorer
Deep codebase exploration agent for architecture understanding, pattern discovery, and comprehensive code analysis. Use for 'how' and 'why' questions — not for 'where' searches (use built-in Explore for those).