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 skills/ryanczak/rexymcp/autonpx skills add ryanczak/rexyMCP --skill autogit clone --depth 1 https://github.com/ryanczak/rexyMCPWrote 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/skills/ryanczak/rexymcp/auto)<a href="https://agentmods.dev/skills/ryanczak/rexymcp/auto"><img src="https://agentmods.dev/badge/skills/ryanczak/rexymcp/auto.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.00059 | $0.03764 |
| Opus 5 | $0.00030 | $0.01882 |
| Sonnet 5 | $0.00012 | $0.00753 |
| Haiku 4.5 | $0.00006 | $0.00376 |
Grade A, and why
auto 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Skill — the opt-in autonomous loop
This skill drives the architect/executor cycle hands-off across a whole milestone: it drafts the next phase, dispatches it, reviews the result, and escalates or re-dispatches on failure — cycling until the milestone closes or a stop condition fires. It exists so a user who wants a hands-off run gets one, without giving up any review rigor.
The one invariant: compose, never fork
This skill composes the existing four skills. It does not reimplement them.
| Loop step | The skill it invokes |
|---|---|
| draft the next phase | architect (§3 phase-doc authoring) |
| dispatch a phase | dispatch |
| review a completed phase | review |
| decide an escalation lever | escalate |
The loop adds only sequencing, the per-phase assist budget, journaling, the five stop conditions, and the loop report. It does not restate the Definition of Done, the bug-report template, the escalation levers, or the status-flip mechanics — each composed skill owns those, and running that skill's procedure verbatim is what keeps an autonomous run identical to an interactive one.
A behavior difference between an interactive run of a step and its autonomous run is a bug, not a feature. If you ever find yourself writing "in auto mode we do X differently," stop — that is the anti-pattern this skill exists to avoid.
Read these first
Before any action:
- Read
<repo>/docs/dev/NEXT.md(the active-phase pointer) and<repo>/docs/dev/WORKFLOW.md§ "Opt-in autonomous loop (off by default)" and § "What Executors Never Decide" (the human-territory list this loop stops on). - Read all four composed skills —
architect,dispatch,review,escalate— so you invoke their procedures unchanged. - Read
<repo>/rexymcp.toml: confirm[executor]+[commands]are present (bootstrap done), and read[escalation] max_assists(the per-phase assist budget, default 3) and[architect] dispatch_model/review_model(the role models for delegation; unset = inherit the session model).
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 · 274 lines · 59 tokens per session scan A 652d77530ca9
auto is a skill published in the GitHub repository ryanczak/rexyMCP (86 stars, last pushed 18d ago), licensed MIT. It adds 59 tokens to every session and 3,764 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…