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 servegit 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/serve)<a href="https://agentmods.dev/skills/trevhud/rote/serve"><img src="https://agentmods.dev/badge/skills/trevhud/rote/serve/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/serve"><img src="https://agentmods.dev/badge/skills/trevhud/rote/serve.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.00088 | $0.01113 |
| Opus 5.5 | $0.00035 | $0.00445 |
| Sonnet 5.5 | $0.00018 | $0.00223 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
serve 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Serve compiled pipelines as MCP tools
rote serve is one MCP server exposing every registered pipeline as a
callable tool. The flow:
rote compile → deploy the runtime → rote register → rote serve → call from Claude
rote serve triggers deployed workflows; it does not host them.
MCP triggering supports the dbos (default), temporal, and
cloudflare runtimes.
The CLI ships on PyPI as rote-cli with an executable named rote,
so every invocation is uvx --from rote-cli rote <args> (never
uvx rote-cli ...). For unreleased features, substitute the source:
uvx --from git+https://github.com/trevhud/rote rote <args>.
1. Check preconditions
- A compile output directory exists (contains
compiled/pipeline.yaml). - The runtime side is running: for DBOS, the emitted app in worker mode
(
python main.py --serveordbos start) against the system database you'll register — enqueued runs sit in statusenqueueduntil that process exists; for Temporal, a worker against the user's cluster; for Cloudflare,wrangler deploydone. If not, stop and help with that first.
2. Register the pipeline
# DBOS (the default). System DB URL: --system-database-url, else
# $DBOS_SYSTEM_DATABASE_URL, else the emitted app's SQLite file
# (derived from <out-dir>/runtime/dbos/main.py).
uvx --from rote-cli rote register <out-dir>
# Temporal (defaults: localhost:7233, namespace "default",
# task queue = pipeline.name, workflow type = the emitted versioned name)
uvx --from rote-cli rote register <out-dir> --runtime temporal
# Cloudflare
uvx --from rote-cli rote register <out-dir> --runtime cloudflare \
--url https://<worker>.workers.dev
This upserts ~/.rote/registry.json. Re-registering updates in place.
After re-compiling a changed skill, register again — the DBOS and
Temporal workflow names are derived from the pipeline content hash and
must stay in sync with the emitted code.
3. Add the MCP server to Claude
rote serve needs the serve extra (FastMCP) plus dbos when any
registered pipeline runs on DBOS, so the spec includes both:
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 Changed · +8 lines ce83b7eff3f0
- 1mo ago First seen · 101 lines · 88 tokens per session scan A c9b451db9fca
serve is a skill published in the GitHub repository trevhud/rote (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 88 tokens to every session and 1,113 once invoked, about $0.0004 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 skills, from other repositories
api-interface-design
Use when designing public APIs, module boundaries, provider adapters, tool schemas, or data contracts.
architecture-patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
fastapi-templates
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
api-design-principles
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.