A coding workflow that replaces unfinished modules in a generated pipeline with working code. It then runs the pipeline from start to finish to check the result.

Use it after generating or compiling a rote pipeline when its modules still raise stub or not-implemented errors.

Generated pipeline applications can contain placeholder functions that fail when called; this workflow turns those placeholders into implementations while preserving the pipeline's defined contracts.

implement — Skill for Claude Code by trevhud/rote

Install

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.

Any agent

npx skills add trevhud/rote --skill implement

Clone the repo

git clone --depth 1 https://github.com/trevhud/rote

Made for: Claude Code.

Or install rote, the plugin that ships this one along with the rest of its 3 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/trevhud/rote/implement/github.svg)](https://agentmods.dev/skills/trevhud/rote/implement)

Your own site

<a href="https://agentmods.dev/skills/trevhud/rote/implement"><img src="https://agentmods.dev/badge/skills/trevhud/rote/implement/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/trevhud/rote/implement"><img src="https://agentmods.dev/badge/skills/trevhud/rote/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 144 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,340 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00144	$0.03340
Opus 5.5	$0.00058	$0.01336
Sonnet 5.5	$0.00029	$0.00668
Haiku 4.5	$0.00014	$0.00334

Measured 5d ago against content hash 50f6058a0308, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement 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.

plugin/skills/implement/SKILL.md · 273 lines

How it starts

The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement the stubs of an emitted pipeline

rote emit and rote compile produce a runnable app whose deterministic steps are scaffolds: every pure_function and external_call node that has no real implementation yet gets a stub that fails on call. Your job is to replace those stubs with working code that honors each node's IR contract, then prove the pipeline runs end to end with rote run.

You write code only in user-owned files. rote owns everything else and regenerates it on the next emit.

The CLI ships on PyPI as rote-cli. Invoke it as uvx --from rote-cli rote <args>, which works on every release (the uvx rote-cli shorthand needs a release newer than 0.14.0). Running a Python app needs that runtime's extra in the same environment, because rote run executes it with its own interpreter: uvx --from 'rote-cli[dbos]' rote run ... for DBOS, 'rote-cli[temporal]' for Temporal. If the user is inside a rote checkout with a .venv, .venv/bin/rote works too.

1. Locate the emitted dir and its IR

The user names the directory, or it is the most recent --out in the conversation. Accept any of:

a rote compile --out dir: IR at compiled/pipeline.yaml, apps under runtime/<target>/ (ask which target if there are several);
a bare emitted runtime dir.

Find the runtime from its marker files, in this order: wrangler.jsonc = cloudflare, src/inngest/ = inngest, dbos-config.yaml + main.py = dbos, dbos-config.yaml alone = dbos-ts, workflow.py + activities.py = temporal, main.py alone = python.

Find the IR the way rote run does: <dir>/pipeline.yaml, then <dir>/../../compiled/pipeline.yaml when the parent is named runtime, then <dir>/../pipeline.yaml. If none exists, ask the user for it. Do not implement from the emitted code alone: the IR is the contract, and the stub docstrings are a lossy rendering of it.

Confirm the directory, runtime, and IR path with the user before editing.

2. Build the TODO list

Get the list from rote rather than by guessing. Re-emitting into the same directory is safe (see section 6) and reports what is still a stub:

Read the full file on GitHub · 273 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/runtimes.md 8.9 KB

Changes

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 · +6 lines 50f6058a0308
6d ago First seen · 267 lines · 144 tokens per session scan A a24d29e55af6

Subscribe to this mod's changes

implement is a skill published in the GitHub repository trevhud/rote (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 144 tokens to every session and 3,340 once invoked, about $0.0006 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-19.

E2E testing Testing agent-skills agentic-ai ai-agents anthropic claude cli

screen-reader-testing

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

wshobson/agents · 39 tokens

e2e-testing-patterns

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

wshobson/agents · 51 tokens

e2e-testing

Use when writing or stabilizing Playwright tests that drive a real browser through multi-step journeys — durable locators, web-first assertions, storageState auth, trace/retries, and flakes that only bite in CI. NOT in-process component tests (that is testing-web), NOT WCAG auditing (that is accessibility), NOT the…

ericrisco/rsc-harness · 79 tokens

implement