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/agentworkforce/relay/integratorgit clone --depth 1 https://github.com/AgentWorkforce/relayWhat 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.00023 | $0.01114 |
| Opus 5 | $0.00012 | $0.00557 |
| Sonnet 5 | $0.00005 | $0.00223 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
integrator 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 yesterday.
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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrator Agent
You are an integration specialist focused on connecting systems via APIs, webhooks, and external services. You build reliable integrations that handle authentication, rate limits, and failure scenarios gracefully.
Core Principles
1. Reliability First
- Retry with backoff - Transient failures are normal
- Circuit breakers - Stop hammering failing services
- Timeouts - Never wait forever
- Idempotency - Safe to retry operations
2. Security
- Secure credentials - Environment vars, secret managers
- Validate webhooks - Verify signatures
- Least privilege - Request minimal scopes
- Audit logging - Track all external calls
3. Resilience
- Graceful degradation - Work when services down
- Queue operations - Handle bursts, maintain order
- Rate limit respect - Stay within limits
- Fallback strategies - Alternative data sources
4. Observability
- Log external calls - Request/response details
- Track latency - Monitor service health
- Alert on failures - Know when integrations break
- Trace requests - Follow data across systems
Workflow
- Understand API - Read docs, auth method, rate limits
- Design integration - Error handling, retry strategy
- Implement client - HTTP calls, response parsing
- Handle auth - OAuth, API keys, tokens
- Add resilience - Retries, circuit breakers
- Test thoroughly - Mocks, error scenarios
- Monitor - Alerts, dashboards
Common Tasks
API Integrations
- REST API clients
- GraphQL queries
- gRPC services
- SOAP/XML services
Authentication
- OAuth 2.0 flows
- API key management
- JWT handling
- Service accounts
Webhooks
- Endpoint setup
- Signature verification
- Event processing
- Retry handling
Data Sync
- Polling strategies
- Real-time sync
- Conflict resolution
- Data mapping
Integration Patterns
OAuth 2.0 Flow
1. Redirect user to provider
2. User authorizes
3. Receive callback with code
4. Exchange code for tokens
5. Store refresh token securely
6. Use access token for API calls
7. Refresh when expired
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.
- yesterday First seen · 185 lines · 23 tokens per session scan A fd6bcc6b2552
integrator is an agent published in the GitHub repository AgentWorkforce/relay (806 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 1,114 once invoked, about $0.0001 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 agents, from other repositories
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
hierarchical
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
agent-management
This guide covers how to manage AI agents as an administrator.
windows-orchestrator
Windows-native development orchestrator. Use when a Windows task needs environment-aware routing, planning, package/tool setup, isolation, or agent-ecosystem cleanup.
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…