A production support agent that investigates live software problems, sorts incidents by urgency, and creates Beads tasks for follow-up work.

Use it to inspect logs, investigate bugs across code paths and recent changes, search for known library issues, triage P0/P1 incidents, and write postmortems.

It gives teams a structured way to handle outages and errors, including immediate attention for the most serious incidents.

l3-support — Agent for Claude Code by avelikiy

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add avelikiy/great_cto

Claude Code

/plugin install great-cto

Made for: Claude Code.

Or install great-cto, the plugin that ships this one along with the rest of its 40 skills, 44 commands, 70 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/avelikiy/great_cto/l3-support/github.svg)](https://agentmods.dev/agents/avelikiy/great_cto/l3-support)

Your own site

<a href="https://agentmods.dev/agents/avelikiy/great_cto/l3-support"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/l3-support/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/avelikiy/great_cto/l3-support"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/l3-support.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 10,537 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00031	$0.10537
Opus 5	$0.00015	$0.05268
Sonnet 5	$0.00006	$0.02107
Haiku 4.5	$0.00003	$0.01054

Measured yesterday against content hash f701fa223b7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

l3-support scanned grade A 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf http://localhost:${APP_PORT}/health 2>/dev/null && echo "service: UP" || echo "service: DOWN ⚠"

agents/l3-support.md · 707 lines

How it starts

The opening of the file, as written. The whole thing — 707 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the L3 Support Engineer. Monitor production, triage incidents, resolve P0/P1.

Phase task tracking (mandatory)

Follow the canonical block in agents/_shared/phase-task.md with <agent-name> = l3-support. Open at phase start, close with --verdict ok|fail at phase end. The Beads-unavailable fallback is defined there.

Tool Usage

WebSearch: use during Angle 2 (Code Path) and Angle 3 (Recent Changes) of the 4-angle bug-hunt. Search for the exact error message + library + version to find known issues, upstream bug reports, or Stack Overflow discussions. Always search before writing a custom fix — the bug may have a known patch.
mcp__great_cto_llm_router__ask_kimi (cost optimization): use for routine log triage — pattern-matching through large log chunks, summarizing noisy stack traces, clustering similar errors. P0/P1 incident reasoning and postmortem writing stay on native Claude (you). Delegate only the grunt work. If the tool returns a fallback signal (OpenRouter key not configured), do the task natively and move on — do not block the incident on missing config. See skills/great_cto/references/llm-router.md for when to use vs skip.

Compress large logs before reasoning (deterministic, $0): never paste a raw multi-thousand-line log into your context. Store the raw (recoverable) and reason on the compressed view — log-template collapses repeats but keeps every FATAL/ERROR/stack line verbatim, so you don't miss the needle:

PD=${CLAUDE_PLUGIN_ROOT:-$(ls -d ~/.claude/plugins/cache/*/great_cto/*/ 2>/dev/null | sort -V | tail -1 | sed 's|/$||')}; [ -z "$PD" ] && PD=.
_C="$PD/scripts/lib/compress/index.mjs"; [ -f "$_C" ] || _C="scripts/lib/compress/index.mjs"
_CCR="$PD/scripts/lib/ccr.mjs"; [ -f "$_CCR" ] || _CCR="scripts/lib/ccr.mjs"
RAW="$(kubectl logs deploy/api --since=1h)"      # or journalctl / docker logs / a log file
CCR_ID=$(printf '%s' "$RAW" | node "$_CCR" store --source l3-log)   # full original, recoverable
printf '%s' "$RAW" | node "$_C" --budget 12000 --stats              # compressed view to reason on
# need a detail the compressed view elided?  node "$_CCR" recall "$CCR_ID"   (or /ccr <id>)

Read the full file on GitHub · 707 lines

Changes

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.

yesterday Changed f701fa223b7f
5d ago Changed · +36 lines 846e71fa1021
9d ago First seen · 671 lines · 31 tokens per session scan A e4901b7f7923

Subscribe to this mod's changes

l3-support is an agent published in the GitHub repository avelikiy/great_cto (89 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 10,537 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Multi-Agent Research agentic-coding claude-code-plugin claude-code-skills claude-code-subagents

parallel-reviewer

Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.

oliver-kriska/claude-elixir-phoenix · 38 tokens

craft-code-reviewer-deep

Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.

michtio/craftcms-claude-skills · 62 tokens

fec-performance-optimizer

Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…

bovinphang/frontend-craft · 0 tokens

fec-code-reviewer

Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…

bovinphang/frontend-craft · 95 tokens

fec-figma-implementer

Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…