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 skills add trevhud/rote --skill setupgit clone --depth 1 https://github.com/trevhud/roteWrote 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/trevhud/rote/setup)<a href="https://agentmods.dev/skills/trevhud/rote/setup"><img src="https://agentmods.dev/badge/skills/trevhud/rote/setup/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/skills/trevhud/rote/setup"><img src="https://agentmods.dev/badge/skills/trevhud/rote/setup.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.00079 | $0.00961 |
| Opus 5.5 | $0.00032 | $0.00384 |
| Sonnet 5.5 | $0.00016 | $0.00192 |
| Haiku 4.5 | $0.00008 | $0.00096 |
Grade A, and why
setup 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 23d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up rote
You relay rote setup. rote asks the questions and makes the plans, and the
user answers them. You never answer a question or approve a plan yourself,
and you never pass --yes.
1. Run it
uvx --from rote-cli rote setup --agent-mode yes --json
It prints one JSON object on stdout. Exit 0 or 1 with status: "done"
means it finished: go to step 3.
2. Each stop: ask, then run next
Exit 2 is a stop with status: "action_required". Tell the user what
ask says, in your own plain words, with the step it belongs to
(step.index of step.total). Keep money and time in it when the plan
spends any. Then wait for their answer.
reason |
What the user decides | What you run |
|---|---|---|
missing_answer |
the question in ask, from choices (skills and servers describe them) |
next[0].command, with the placeholder replaced by their answer as answer_with says |
confirmation_required |
yes or no to the plan | yes: next[0].command, no: next[1].command |
authorization_pending |
approve each logins[].authorization_url in their browser |
once they say done: each rote mcp login --complete command in next, then the last next command |
person_required |
run next[0].command in their own terminal (you cannot) |
once they say done: the last next command |
Run exactly the command next gives. rote remembers earlier answers, so it carries only the new one.
Never add a flag it does not name. An error (exit 1, error) names its fix:
tell the user, and run rote setup again once it is fixed.
When rote asks which servers to log in to (step login) and says the
skill does not say which servers it calls, read the skill and pick the
servers whose tools it calls.
When rote asks which skill to compile (reason: missing_answer, step
skill), read the SKILL.md of each choice before you answer, and
recommend one to the user by the rule below, with one line on why. Say
which choices it rules out.
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.
- 23d ago Changed · +31 lines 5654244bfff0
- 24d ago First seen · 50 lines · 79 tokens per session scan A 024ee8bd9db1
setup is a skill published in the GitHub repository trevhud/rote (8 stars, last pushed 3d ago), licensed Apache-2.0. It adds 79 tokens to every session and 961 once invoked, about $0.0003 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-10-26.
setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| setuptrevhud/rote | Skill | 8 | 3d ago | Apache-2.0 | A | 79 | Claude Code |
| api-interface-designMohitGoyal09/AgentForge | Skill | 67 | 28d ago | MIT | A | 23 | Claude Code, Codex |
| exploreMohitGoyal09/AgentForge | Skill | 67 | 28d ago | MIT | A | 15 | Claude Code, Codex |
| watchKostakurta8/roundtable | Skill | 22 | 1mo ago | MIT | A | 42 | Claude Code |
| gifKostakurta8/roundtable | Skill | 22 | 1mo ago | MIT | A | 45 | Claude Code |
| statsKostakurta8/roundtable | Skill | 22 | 1mo ago | MIT | A | 49 | Claude Code |
| agent-goal-skillDallionking/agent-goal-skill | Skill | 11 | 4mo ago | MIT | A | 113 | Claude Code |