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 skills/undertone0809/rudder/rudder-docsnpx skills add Undertone0809/rudder --skill rudder-docsgit clone --depth 1 https://github.com/Undertone0809/rudderWrote 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/undertone0809/rudder/rudder-docs)<a href="https://agentmods.dev/skills/undertone0809/rudder/rudder-docs"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/rudder-docs.svg" alt="Measured on agentmods" 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.00120 | $0.01866 |
| Opus 5 | $0.00060 | $0.00933 |
| Sonnet 5 | $0.00024 | $0.00373 |
| Haiku 4.5 | $0.00012 | $0.00187 |
Grade A, and why
rudder-docs 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 6d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rudder Docs
Provide authoritative, current guidance about Rudder. This is Rudder's documentation and self-knowledge entry point, not a workflow that must run merely because the agent is hosted by Rudder.
If this body is already present in the prompt but the current request does not need Rudder guidance, do not perform a docs lookup. Continue the user's actual task using the current tools and context.
Purpose And Non-Goals
Classify the Rudder question, consult the smallest authoritative source set, and answer with clear provenance. Use current evidence instead of memory for commands, interfaces, versioned behavior, and product contracts.
This router does not make an ordinary hosted task into a Rudder workflow. It does not provide a command catalog, replace runtime-owned execution rails, or authorize an operation merely because it documents that operation.
Classify The Request
Choose one primary class before retrieving evidence:
- Current capability or installed command: what this run exposes, which CLI syntax is installed, or whether an exact operation is supported.
- Public product guidance: how a user should use or configure Rudder.
- Product contract: the intended semantics or invariant for a Rudder feature.
- Contributor or source behavior: architecture, implementation location, tests, API compatibility, or an exact source-level explanation.
- Discrepancy, troubleshooting, or release: observed behavior differs from guidance, a Rudder operation failed, or the answer depends on a version.
- Explicit creation or authoring: the user asks to create, hire, or configure a Rudder Agent, or to scaffold, develop, or verify a Rudder Plugin.
- Offline or restricted: the preferred live, public, or source evidence is unavailable.
For a mixed question, resolve each material claim through its owning source instead of applying one global priority.
Choose The Source Route
Current Run Capability And Installed CLI
Inspect exposed typed Rudder tools first. If capability discovery is needed,
use rudder agent capabilities --json; then use rudder --version and the
exact installed command's --help. Consult the relevant part of the CLI
reference only after those live checks. Use the API reference only for an
explicit internal, debugging, or compatibility question.
What ships with it
9 files 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.
- evals/retrieval-authority-evals.json 13 KB
- evals/trigger-evals.json 4.0 KB
- references/agent-creation.md 7.2 KB
- references/api-reference.md 13 KB
- references/cli-reference.md 28 KB
- references/operating-practices.md 13 KB
- references/organization-skills.md 6.6 KB
- references/plugin-authoring.md 1.8 KB
- references/source-map.md 8.7 KB
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.
- 6d ago First seen · 178 lines · 120 tokens per session scan A d3854dbae715
rudder-docs is a skill published in the GitHub repository Undertone0809/rudder (288 stars, last pushed yesterday), licensed Apache-2.0. It adds 120 tokens to every session and 1,866 once invoked, about $0.0006 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…