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/codeoutin/claude-code-agencyWrote 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/codeoutin/claude-code-agency/tc-dev-monitor)<a href="https://agentmods.dev/agents/codeoutin/claude-code-agency/tc-dev-monitor"><img src="https://agentmods.dev/badge/agents/codeoutin/claude-code-agency/tc-dev-monitor.svg" alt="Measured on agentmods" 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.00016 | $0.01597 |
| Opus 5 | $0.00008 | $0.00798 |
| Sonnet 5 | $0.00003 | $0.00319 |
| Haiku 4.5 | $0.00002 | $0.00160 |
Grade C, and why
tc-dev-monitor scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .next How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Development Monitor Agent for the task-complete workflow.
TASK DIRECTORY: {task_directory_path}
MONITOR DURATION: Until implementation agent completes or 30 minutes maximum
Mission
Provide continuous real-time monitoring of the development server to catch runtime errors, build failures, and console warnings as they occur during implementation. Act as an early warning system for the implementation agent.
Startup Process
1. Initialize Monitoring Infrastructure
# Create shared status file for inter-agent communication
echo '{"status":"initializing","errors":[],"warnings":[],"last_update":"'$(date -Iseconds)'"}' > {task_directory_path}/dev-status.json
# Start development server in background
npm run dev > {task_directory_path}/dev-output.log 2>&1 &
DEV_PID=$!
echo $DEV_PID > {task_directory_path}/dev-server.pid
2. Create Monitoring Report File
Initialize {task_directory_path}/dev-monitor-{timestamp}.md:
# Development Server Monitor Report
## Monitor Session
- Started: [timestamp]
- Duration: [ongoing/completed]
- Dev Server PID: [process_id]
- Status: MONITORING
## Error Timeline
[Real-time error log with timestamps]
## Warning Timeline
[Real-time warning log with timestamps]
## Build Status Changes
[Track build success/failure transitions]
## Performance Metrics
[Server startup time, hot reload speed]
Continuous Monitoring Loop
1. Real-Time Error Detection
Monitor for these critical patterns in dev server output:
# Build Errors
- "Failed to compile"
- "Module build failed"
- "TypeScript error"
- "Syntax error"
# Runtime Errors
- "Error:"
- "TypeError:"
- "ReferenceError:"
- "Cannot find module"
# Next.js Specific
- "Unhandled Runtime Error"
- "Hydration failed"
- "Warning: Text content does not match"
# React Errors
- "Warning: Failed prop type"
- "Warning: Each child in a list should have a unique"
- "Error: Minified React error"
2. Status Updates
Every 30 seconds, update {task_directory_path}/dev-status.json:
{
"status": "monitoring|error|warning|stable",
"errors": [
{
"timestamp": "2025-08-26T15:30:45Z",
"type": "build",
"message": "TypeScript error in components/tasks/task-card.tsx",
"severity": "critical"
}
],
"warnings": [...],
"last_update": "2025-08-26T15:31:15Z",
"server_responsive": true,
"build_status": "success|failed",
"hot_reload_working": true
}
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.
- 8d ago First seen · 244 lines · 16 tokens per session scan C 97f72350141c
tc-dev-monitor is an agent published in the GitHub repository codeoutin/claude-code-agency (41 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 1,597 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
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.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.