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 agents/undertone0809/rudder/control-toolsgit clone --depth 1 https://github.com/Undertone0809/rudderWhat 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.00000 | $0.05561 |
| Opus 5 | $0.00000 | $0.02780 |
| Sonnet 5 | $0.00000 | $0.01112 |
| Haiku 4.5 | $0.00000 | $0.00556 |
Grade A, and why
control-tools 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 2d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Built-in Rudder Tools
AGENT.CONTROL.TOOLS.001
Contract Summary
Rudder exposes a first-party rudder-tools MCP server for supported
agent runtimes. The server presents the stable agent-v1 command contract as
typed MCP tools using rudder_<capability_id> names. Each tool publishes an
exact capability-specific input schema with required fields, accepted types,
bounded sizes, and no additional properties. Rudder conditionally projects
the Built-in Browser tool set from trusted runtime capability state, dispatches
built-in Rudder tools directly through Rudder's runtime API context when
supported, falls back to the existing Rudder CLI command path for remaining
capabilities, and gets organization, agent, run, API, and project-library
identity only from runtime-owned environment.
Organization-managed external MCP servers are a separate runtime surface.
Rudder projects each enabled external connection as an independent run-scoped
proxy through the provider-neutral managedExternalMcpBindings contract. These
proxies do not add tools to, rename, replace, share credentials with, or weaken
the identity boundary of the first-party rudder-tools server.
Intent / User Job
Runtime agents need a reliable Rudder tool surface for issue, run, chat, automation, library, approval, skill, agent, and bounded Browser operations. Operators need this surface to be typed, auditable, and scoped to the current run instead of relying on model-invented shell commands or user/home MCP configuration.
Why / Design Reasoning
The bundled rudder-docs skill remains the compatibility reference for exact
CLI command details, but agent runtimes that support MCP should prefer
first-party Rudder tools. The skill is always discoverable; that does not mean
an agent must read it on every run. MCP gives the model a typed schema, stable
tool names, and a clear transport boundary while preserving CLI compatibility
for capabilities that have not moved to direct runtime API dispatch.
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.
- 2d ago First seen · 410 lines · 0 tokens per session scan A 977278764cc0
control-tools is an agent published in the GitHub repository Undertone0809/rudder (287 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 5,561 tokens. 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.