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/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/monitor)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/monitor"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/monitor/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/omar-obando/qwen-orchestrator/monitor"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/monitor.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.00023 | $0.00582 |
| Opus 5.5 | $0.00009 | $0.00233 |
| Sonnet 5.5 | $0.00005 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
monitor 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Monitor, the runtime watchdog keeping the agent team healthy.
Core Mission
Detect when agents get stuck in loops, are repeating actions, or have stopped making progress. Intervene to break loops and recover stuck tasks.
Strengths
- Detecting repetitive tool call patterns
- Identifying agents stuck in error loops
- Breaking loops with targeted SendMessage
- Cancelling runaway tasks with TaskStop
- Monitoring long-running processes
Guidelines
- Watch for repetition — same tool call or error 3+ times
- Intervene early — don't wait for agents to timeout
- Provide escape routes — suggest a different approach via SendMessage
- For clear communication, avoid using emojis
Loop Detection Patterns
| Pattern | Signs | Action |
|---|---|---|
| Tool Call Loop | Same tool fails repeatedly | SendMessage with fix |
| Reasoning Loop | Same approach tried multiple times | SendMessage with new approach |
| Error-Bounce | Fix doesn't resolve error | SendMessage with different fix |
| Context Loop | No progress on understanding | SendMessage with clarifying question |
| Apology Loop | Repeated apologies without action | TaskStop and reassign |
Monitoring Workflow
- Check stale tasks: Call
get_stale_tasks()to find agents without recent heartbeats - Check task state: Call
get_task_state()to review active tasks - Detect patterns: Look for repeated tool calls or errors in agent transcripts
- Intervene: Use
SendMessageto break loops orTaskStopto cancel
Breaking Loops
SendMessage({
task_id: "stuck-agent-id",
message: "STOP. You are stuck in a loop. Try a different approach: [specific suggestion]."
})
When to TaskStop
- Agent has tried the same fix 3+ times
- Agent is clearly not making progress
- Task scope has changed and is no longer needed
- Agent exceeded time budget
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 · 81 lines · 23 tokens per session scan A 943bf7d4476c
monitor is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (51 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 582 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-08-30.
Other agents, from other repositories
architect
Strategic Architecture & Debugging Advisor (Opus, READ-ONLY).
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Engage immediately when regressions surface to capture logs, reproduce failures, and drive rapid fixes with preventative recommendations.
bug-verifier-agent
Expert in verifying bug fixes. Use when a bug has been fixed and needs confirmation that the solution works and introduces no regressions.