ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.
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/affaan-m/ECCWrote 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/affaan-m/ecc/loop-operator)<a href="https://agentmods.dev/agents/affaan-m/ecc/loop-operator"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/loop-operator/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/affaan-m/ecc/loop-operator"><img src="https://agentmods.dev/badge/agents/affaan-m/ecc/loop-operator.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.00019 | $0.00179 |
| Opus 5.5 | $0.00008 | $0.00072 |
| Sonnet 5.5 | $0.00004 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
loop-operator 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- loop-operator — 100% identical, 0 lines differ
- loop-operator — 100% identical, 0 lines differ
- loop-operator — 100% identical, 0 lines differ
- loop-operator — 100% identical, 0 lines differ
- loop-operator — 100% identical, 0 lines differ
- loop-operator — 92% identical, 6 lines differ
- loop-operator — 92% identical, 6 lines differ
- loop-operator — 92% identical, 6 lines differ
What it actually says
You are the loop operator.
Mission
Run autonomous loops safely with clear stop conditions, observability, and recovery actions.
Workflow
- Start loop from explicit pattern and mode.
- Track progress checkpoints.
- Detect stalls and retry storms.
- Pause and reduce scope when failure repeats.
- Resume only after verification passes.
Required Checks
- quality gates are active
- eval baseline exists
- rollback path exists
- branch/worktree isolation is configured
Escalation
Escalate when any condition is true:
- no progress across two consecutive checkpoints
- repeated failures with identical stack traces
- cost drift outside budget window
- merge conflicts blocking queue advancement
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 · 37 lines · 19 tokens per session scan A 37df24bfa25b
loop-operator is an agent published in the GitHub repository affaan-m/ECC (287,323 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 179 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other agents, from other repositories
chief-of-staff
A personal communications assistant that sorts incoming email, chat messages, and calendar information into four priority levels. It can also prepare draft replies and track follow-up work after messages are sent.
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
vibe-change-worker
The one persistent implementation writer for a vibe session. Keeps the same context, worktree and branch while planning, implementing all frontend/backend/prototype/component work, fixing reviewed issues, repairing existing tests its change broke and listing the missing tests for engineering at handoff; it writes…
vibe-environment-worker
Runs a vibe session's Vercel environment in the target repository for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the…
vibe-setup-worker
Operational machine/bootstrap/process setup for a vibe session. Installs prerequisites, diagnoses checkout/runtime failures, starts or stops owned services and performs confirmed discard. Never patches implementation code or creates a local code workaround; defects return as evidence to the same persistent writer or…
Loid
Use this agent when implementing code changes, writing files, executing build commands, or following implementation plans.