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.
/plugin marketplace add avelikiy/great_cto/plugin install great-ctoWrote 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/commands/avelikiy/great_cto/inbox)<a href="https://agentmods.dev/commands/avelikiy/great_cto/inbox"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/inbox/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/commands/avelikiy/great_cto/inbox"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/inbox.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.00940 |
| Opus 5 | $0.00010 | $0.00470 |
| Sonnet 5 | $0.00004 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
inbox 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 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.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the great_cto Inbox command. Show the CTO everything that needs attention right now. Keep the response under 30 lines.
Step 1 — Run helper, write to file (no inline expansion)
HOURS="${1:-24}"
PLUGIN_DIR=${CLAUDE_PLUGIN_ROOT:-$(ls -d ~/.claude/plugins/cache/*/great_cto/*/ 2>/dev/null | sort -V | tail -1 | sed 's|/$||')}
HELPER="${PLUGIN_DIR}/scripts/cmd-data/inbox-data.sh"
[ -f "$HELPER" ] || HELPER="$(pwd)/scripts/cmd-data/inbox-data.sh"
OUT_DIR=".great_cto/cache"; mkdir -p "$OUT_DIR"
OUT="${OUT_DIR}/inbox-out.txt"
HOURS="$HOURS" bash "$HELPER" > "$OUT" 2>&1
SIZE=$(wc -c < "$OUT" 2>/dev/null || echo 0)
LINES=$(wc -l < "$OUT" 2>/dev/null || echo 0)
echo "INBOX_READY hours=$HOURS out=$OUT size=${SIZE}B lines=${LINES}"
Don't pipe helper output to stdout — that re-expands it into your
prompt and may trip Prompt is too long on heavy sessions.
Step 2 — Read the file
Use the Read tool on the out= path, default first 200 lines.
Sections (only present when relevant, separated by blank lines):
## ARCHETYPE_CONFIDENCE, ## OPEN_GATES, ## STALE_GATES,
## P0_OPEN, ## BLOCKED, ## RECENT_ACTIVITY, ## SLO_BURN,
## DORA_CFR, ## GATE_DRIFT, ## COST_ALERT, ## ON_CALL,
## RFC_OVERDUE.
Step 2b — Strict-mode governance (signed exceptions)
Surface the audited gate-bypass trail so nothing expires silently. Active exceptions are sanctioned overrides; expired/revoked ones are debt to remediate.
PD=${CLAUDE_PLUGIN_ROOT:-$(ls -d ~/.claude/plugins/cache/*/great_cto/*/ 2>/dev/null | sort -V | tail -1 | sed 's|/$||')}; [ -z "$PD" ] && PD=.
node "$PD/scripts/lib/exceptions.mjs" list 2>/dev/null || node scripts/lib/exceptions.mjs list 2>/dev/null || true
Render any ✗ (expired/revoked/tampered) exceptions as ⚠️ High ("signed exception
EXC-… expired — remediate the work it covered or re-sign"). Active ones expiring within 7
days → 🔔 Medium. If a release is imminent, also run gate-check.mjs gate:ship and show
any blocking tasks. See /exception.
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 d7e32fb0ea99
- 5d ago First seen · 85 lines · 19 tokens per session scan A 1ec95c99fd2b
inbox is a command published in the GitHub repository avelikiy/great_cto (89 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 940 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
auto-task
Create an agent team for autonomous workflow: plan (Architect teammate + PM teammate) → develop (Developer teammate + Code-tester teammate + QA-tester teammate + Reviewer teammate) → report (no approval gate).
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
fec-review
Conduct a standardized review of the specified file or recently changed front-end code, output a graded review report and save it as a Markdown file.
develop
Implement skill development issues with TDD-governed workflow.
fec-doc-sync
Sync README, docs, environment variables, scripts, API/routing/component descriptions and deployment instructions from code and project sources of truth.
design-review
Compare design (Figma URL or mockup image) against implementation to detect UI mismatches (colors, layout, typography).