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/custom-integrationsgit 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.06121 |
| Opus 5 | $0.00000 | $0.03061 |
| Sonnet 5 | $0.00000 | $0.01224 |
| Haiku 4.5 | $0.00000 | $0.00612 |
Grade A, and why
custom-integrations 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 — 460 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Custom Integrations
AGENT.CUSTOM.INTEGRATIONS.001
Contract Summary
Rudder supports the existing custom_api and legacy mcp_server records plus
organization-owned managed MCP connections for Supabase, Linear, Notion, GitHub,
and custom servers. Managed connections own provider, transport, external
scope, access mode, lifecycle, safe non-secret configuration, discovered tools,
agent bindings, and redacted dispatch evidence. OAuth grants and temporary
OAuth sessions are separate encrypted credential records; GitHub uses a
personal access token stored in the same encrypted managed-secret boundary.
Public connection summaries expose credential presence only, never secret
identifiers or values. External MCP credentials stay server-side throughout
authorization, discovery, and dispatch. Every managed connection has immutable
organization or agent scope and its own credential boundary. Supabase,
Linear, Notion, and GitHub allow one canonical connection per provider and
target: one Organization connection plus one independent connection for each
Agent. Custom MCP remains multi-instance within either scope. When both
official scopes exist, the Agent connection takes precedence. Operators assign
coarse-grained Agent access instead of managing individual tool checkboxes.
Plugin import may prepare a disabled custom MCP draft through this same service,
but package metadata never supplies runtime admission, credentials, or Agent
access. The operator continues setup and activation through the managed MCP
boundary.
Intent / User Job
Operators need to connect internal APIs, remote MCP servers, and organization specific tools to agent work loops without waiting for each provider to become a first-party Rudder integration. Some tools are shared infrastructure; others are personal or identity-bound and must attach to exactly one agent.
Why / Design Reasoning
Custom integrations are agent-visible runtime capabilities, not generic global settings. The product separates them from fixed provider integrations such as Feishu because fixed providers may have provider-specific identity, chat, and runtime semantics. Custom integrations need explicit organization, owner-agent, binding, tool, credential, and audit records so Rudder can enforce scope before any prompt or tool-call surface sees them.
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 · 460 lines · 0 tokens per session scan A 7e339261008c
custom-integrations 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 6,121 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
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.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.