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/avelikiy/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/promote)<a href="https://agentmods.dev/commands/avelikiy/great_cto/promote"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/promote/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/promote"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/promote.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.00029 | $0.03007 |
| Opus 5 | $0.00015 | $0.01503 |
| Sonnet 5 | $0.00006 | $0.00601 |
| Haiku 4.5 | $0.00003 | $0.00301 |
Grade A, and why
promote 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 6d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the great_cto promotion command. When a POC has shipped
(/poc decide → SHIP), /promote <slug> runs the audits that POC mode
skipped — turning throwaway POC code into production-grade work.
Guard: target POC exists and is marked Shipped
SLUG="$1"
TARGET="${2:-production}"
[ -z "$SLUG" ] && { echo "Usage: /promote <poc-slug> [mvp|production]"; exit 0; }
POC_FILE="docs/poc/POC-${SLUG}.md"
[ ! -f "$POC_FILE" ] && { echo "No POC found at $POC_FILE"; exit 0; }
STATUS=$(grep -m1 "^\*\*Status\*\*:" "$POC_FILE" | sed 's/.*: //')
if [ "$STATUS" != "Shipped" ]; then
echo "POC-${SLUG} status is '${STATUS}', not 'Shipped'."
echo "Run /poc decide first to complete the POC ritual."
exit 0
fi
[ "$TARGET" != "mvp" ] && [ "$TARGET" != "production" ] && { echo "Target must be 'mvp' or 'production'"; exit 0; }
Promotion audit — run in order
The promotion audit fills in what POC mode skipped. Each step is a gate — if it fails, promotion halts and the CTO addresses the gap before continuing. Do not silently pass.
Step 1 — Full ARCH document
POC mode allowed a 1-pager. Production requires a full ARCH.
- Invoke
architectagent via Agent tool with instruction: "Expand POC- into a full ARCH document atdocs/architecture/ARCH-<slug>.md. Use the POC hypothesis, criteria, and evidence as input. Include all standard sections (Problem, Decision with alternatives, Components, API contracts, DB migration, Non-goals, Implementation tasks, DoD, Cost Estimate, Requirements Checklist). Respect archetype-specific requirements — if archetype is ai-system / commerce / web3 / iot-embedded / regulated / fintech, the## Securitysection is mandatory." - Verify output exists:
[ -f "docs/architecture/ARCH-${SLUG}.md" ] || { echo "BLOCKED: ARCH doc not produced"; exit 1; }
Step 2 — Threat model (archetype-aware, v1.0.134)
ARCHETYPE=$(grep "^archetype:" .great_cto/PROJECT.md | awk '{print $2}')
TM="docs/sec-threats/TM-${SLUG}.md"
mkdir -p docs/sec-threats
case "$ARCHETYPE" in
ai-system|agent-product)
# Delegate to ai-security-reviewer specialist (v1.0.134+) — full OWASP LLM Top 10 coverage.
# PoC TM was 3 sections minimum; production needs full 6 sections + sign-off table.
echo "Promote: invoke ai-security-reviewer for full TM at $TM (was PoC lite version)"
# Task(subagent_type='ai-security-reviewer', prompt='full pre-impl TM for promotion of ${SLUG}')
;;
commerce|web3|iot-embedded|regulated|fintech)
echo "Archetype '$ARCHETYPE' requires full threat model."
# Invoke /sec threat ${SLUG} (security-officer pre-impl mode)
;;
*)
echo "Threat model optional for archetype '$ARCHETYPE' — recommended if feature touches auth/payments/PII."
;;
esac
# Hard halt: TM file exists + Critical/High threats signed off (no __pending__)
if [ ! -f "$TM" ]; then
case "$ARCHETYPE" in
ai-system|agent-product|commerce|web3|iot-embedded|regulated|fintech)
echo "BLOCKED: archetype $ARCHETYPE requires $TM before /promote can flip mode" >&2
exit 1
;;
esac
fi
if [ -f "$TM" ] && grep -E "^\| (P|F)-[0-9]+" "$TM" 2>/dev/null | grep -E "Critical|High" | grep -q "__pending__"; then
echo "BLOCKED: $TM has Critical/High threats with __pending__ mitigations. Run security-officer post-impl review." >&2
exit 1
fi
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.
- 6d ago First seen · 276 lines · 29 tokens per session scan A abb60833cae7
promote is a command published in the GitHub repository avelikiy/great_cto (89 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 3,007 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).