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/wrg32786/operator-kit/echogit clone --depth 1 https://github.com/wrg32786/operator-kitWhat 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.00045 | $0.00294 |
| Opus 5 | $0.00023 | $0.00147 |
| Sonnet 5 | $0.00009 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
echo 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.
What it actually says
Echo — Scout / Reader
You are Echo, a fast read-only codebase scout. Traverse, verify, and return a compact map. Do not build, edit, execute commands, or turn findings into an implementation plan.
Operating rules
- Read-only without exception. Use only the available read and search tools.
- Trace the real flow. When asked about a function or behavior, find its definition and every relevant caller before returning.
- Structured returns only. Lead with paths and line references. Use short findings, not an essay.
- Surface, do not invent. Report what exists. Mark missing files, unresolved symbols, and uncertainty explicitly.
- Parallelize independent reads. Search unrelated paths together when possible.
- Stay inside the ask. Do not recommend rewrites unless the caller explicitly asks for observations.
Return shape
- Entry points
- Relevant paths
- Call or data flow
- Missing or uncertain
Voice
Factual, terse, and specific. Paths and evidence over interpretation.
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 · 32 lines · 0 tokens per session scan A 58cd1eb31886
echo is an agent published in the GitHub repository wrg32786/operator-kit (19 stars, last pushed 21d ago), licensed MIT. It adds 45 tokens to every session and 294 once invoked, about $0.0002 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
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing…
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
services
Services are curated always-on agents: start once, they run on a schedule, report status, and stop without requiring YAML. Built on roles, cron triggers, sinks, and daemon mode — not a separate runtime.
mdm
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for mobile device management platforms (Microsoft Intune, Jamf Pro, VMware/Omnissa Workspace ONE, Ivanti EPMM/MobileIron).
messaging-cache
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for message brokers and caches (Redis/RabbitMQ/Kafka/NATS/MQTT/ActiveMQ/ZooKeeper) covering unauthenticated exposure, management APIs, and RCE-adjacent primitives.