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.
git clone --depth 1 https://github.com/wrg32786/operator-kitWrote 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/agents/wrg32786/operator-kit/echo)<a href="https://agentmods.dev/agents/wrg32786/operator-kit/echo"><img src="https://agentmods.dev/badge/agents/wrg32786/operator-kit/echo/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/wrg32786/operator-kit/echo"><img src="https://agentmods.dev/badge/agents/wrg32786/operator-kit/echo.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00294 |
| Opus 5.5 | $0.00000 | $0.00118 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $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 1mo 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.
- 1mo ago First seen · 32 lines · 0 tokens per session scan A 58cd1eb31886
echo is an agent published in the GitHub repository wrg32786/operator-kit (20 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 294 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
streaming-reviewer
Streaming / event-driven pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off delivery-guarantee + ordering decisions before senior-dev claims tasks.
ci-resolver
Use when CI or a build is red. Names each red check's cause (false test, broken gate, real regression, flaky), lands a minimal fix in its own commit, proves green. Never skips a check.
reliability-engineer
Use on flagship work for the reliability review dimension — offline behaviour, retries, idempotency, sync conflict resolution, state restoration, and recovery from interruption. Conditional role. Broad enough to need its own pass; a checklist item inside code review is where it has always been skipped.
factory-ci-doctor
Diagnostician for one red GitHub Actions run. Spawn it after a run has failed — never to wait for one (gh run watch --exit-status does that for free) — with the repo and run ID or PR number, so the failed-job logs never enter the caller's context. It returns the culprit job/step, the offending log lines, and a TICKET…
ciel-quality-guild
CIEL's elite quality and debugging guild. Specializes in refactoring, E2E testing, and API integrity.
test-runner
Runs tests, identifies failures, and fixes them. Use proactively after code changes to verify correctness. Reports results concisely and focuses on minimal fixes.