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/poc)<a href="https://agentmods.dev/commands/avelikiy/great_cto/poc"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/poc/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/poc"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/poc.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.00054 | $0.05764 |
| Opus 5.5 | $0.00022 | $0.02306 |
| Sonnet 5.5 | $0.00011 | $0.01153 |
| Haiku 4.5 | $0.00005 | $0.00576 |
Grade A, and why
poc 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 26d 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 — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the great_cto POC-mode runner. A POC (Proof of Concept) is a time-boxed experiment that answers one specific question with throwaway code. Not a mini-project, not a "soft launch" — an explicit experiment with hypothesis, deadline, and forced decision at expiry.
Guard: great_cto not initialised
[ -f .great_cto/PROJECT.md ] || { echo "No PROJECT.md found. Run /start first, then /poc."; exit 0; }
Sub-command dispatch
Parse $1 as the sub-command. Supported forms:
/poc start <hypothesis>→ new POC;/poc <hypothesis>is the same (anything that's not a reserved keyword)/poc decide→ ritual decision at expiry/poc extend <days>→ extend timebox once (max 1 extension)/poc status→ show current POC state (also bare/poc)/poc promote <poc-slug> [mvp|production]→ promotion audit for a shipped POC
SUB="$1"
case "$SUB" in
start) ACTION=start; shift; HYPOTHESIS="$*" ;;
decide) ACTION=decide ;;
extend) ACTION=extend ;; # $2 = days
status|"") ACTION=status ;;
promote) ACTION=promote; shift ;; # now $1 = slug, $2 = mvp|production
*) ACTION=start; HYPOTHESIS="$*" ;; # `/poc <hypothesis>` = `/poc start <hypothesis>`
esac
Action: start — new POC
Triggered by /poc start <hypothesis>, or by /poc <hypothesis> when $1 is not
decide, extend, status or promote. The rest of the input is the hypothesis
string ($HYPOTHESIS).
Step 1 — Check for active POC
ACTIVE=$(grep "^mode:\s*poc" .great_cto/PROJECT.md 2>/dev/null)
if [ -n "$ACTIVE" ]; then
SLUG=$(grep "^poc_slug:" .great_cto/PROJECT.md | awk '{print $2}')
EXPIRES=$(grep "^poc_expires:" .great_cto/PROJECT.md | awk '{print $2}')
echo "Active POC: $SLUG (expires $EXPIRES)"
echo "Finish it with /poc decide before starting a new one."
exit 0
fi
If an active POC exists, refuse. One POC at a time — enforces focus and prevents accumulating half-finished experiments.
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.
- 26d ago Changed · +286 lines · +23 tokens per session b10bf55a41c9
- 1mo ago First seen · 283 lines · 31 tokens per session scan A 3b943d50513d
poc is a command published in the GitHub repository avelikiy/great_cto (105 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 5,764 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
monitor
Pull review comments from a GitHub PR or GitLab MR and plan/dispatch SWE work to address them.
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.
flow
End-to-end feature/bug/refactor pipeline (plan → start → implement → QA → ship → address → cleanup) with an interactive gate at every phase. Resumable via /orc:resume. --jira links a ticket. Workspace-aware.
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.