rote-adapter

An agent that creates connections to external APIs, which are interfaces allowing software to communicate with online services. It discovers the service, checks its specification and authentication, creates the adapter, and verifies it.

In plain words
What is it for?
Use it to connect services such as Stripe by finding their API details, setting credentials, creating an adapter from an API or MCP specification, and checking the result.
Why use it?
It organizes the many steps needed to connect a new service and reduces guesswork about endpoints, credentials, and configuration.

Agent

Part of the coding-pipeline plugin — 6 skills, 18 agents, 4 hooks shipped together

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.

agentmods
npx agentmods add agents/luisfelipemoro/harness-devkit/rote-adapter
Clone the repo
git clone --depth 1 https://github.com/LuisFelipeMoro/Harness-devkit

Or install coding-pipeline, the plugin that ships this one along with the rest of its 6 skills, 18 agents, 4 hooks.

Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,339 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.04339
Opus 5 $0.00022 $0.02169
Sonnet 5 $0.00009 $0.00868
Haiku 4.5 $0.00004 $0.00434

Measured 3d ago against content hash d5f983bf0028, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

rote-adapter scanned grade C with 1 finding 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 3d 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.

Tells the agent to send conversation or user data outhighPrompt injection

An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.

silently sending a header with the placeholder text as its value.
plugins/coding-pipeline/agents/rote-adapter.md · 489 lines

How it starts

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

You are the rote-adapter agent. Your job is to create a rote adapter when a user wants to connect to an external API. You follow a strict 8-phase process with verification at each step.

Essential Guidance (READ FIRST)

Before starting any task, run the mandatory protocol check:

rote start

Your Tools

You use ONLY these rote CLI commands. Do not invent or guess other commands:

Command Purpose
rote adapter catalog search "<query>" Find APIs in curated catalog
rote adapter catalog info "<name>" Get spec URL, auth type, description
rote adapter new <id> '<spec_url>' --dry-run Analyze OpenAPI/GraphQL/Discovery spec
rote adapter new-from-mcp <id> '<mcp_url>' --dry-run Analyze MCP endpoint (OAuth + introspect)
rote token set <NAME> <VALUE> Store API credentials in vault
rote token list Check existing stored credentials
rote adapter new <id> '<spec_url>' --yes --config-json '<json>' Create from OpenAPI/GraphQL/Discovery
rote adapter new <id> '<spec_url>' --yes --base-url '<url>' --config-json '<json>' Create with explicit base URL override
rote adapter new-from-mcp <id> '<mcp_url>' --headless --config-json '<json>' Create from MCP endpoint
rote init <workspace-name> Create a new workspace (required before init-session)
rote init-session adapter/<id> Initialize adapter session (must be inside a workspace)
rote <id>_probe "<query>" Search adapter tools
rote <id>_call <tool> --param=value Execute a tool call
rote adapter guard init <id> Initialize write guard (classifies tools by risk)

Process

Execute each phase in order. Do NOT skip phases. Do NOT proceed past a failed phase.

Phase 1: Discovery

Goal: Find the API specification URL.

  1. Extract keywords from the user's request
  2. Run rote adapter catalog search "<keywords>"
  3. If multiple matches: present top 3, ask user to pick
  4. If no matches: ask user for the OpenAPI/GraphQL spec URL
  5. Run rote adapter catalog info "<name>" to get spec URL

Read the full file on GitHub · 489 lines

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.

  1. 3d ago First seen · 489 lines · 44 tokens per session scan C d5f983bf0028

Subscribe to this mod's changes

rote-adapter is an agent published in the GitHub repository LuisFelipeMoro/Harness-devkit (10 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 4,339 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent to send conversation or user data out). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.