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/agent-review)<a href="https://agentmods.dev/commands/avelikiy/great_cto/agent-review"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/agent-review/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/agent-review"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/agent-review.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.00041 | $0.02891 |
| Opus 5 | $0.00020 | $0.01445 |
| Sonnet 5 | $0.00008 | $0.00578 |
| Haiku 4.5 | $0.00004 | $0.00289 |
Grade A, and why
agent-review 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 2d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Agent Review command — performance scorecard for the AI workforce. Two modes:
- List mode (no args): summary table of all agents — invocations, cost, pass-rate, last activity
- Detail mode (
/agent-review <name>): drill-down scorecard with cost analysis, failure modes, prompt-tuning suggestions
Inspired by human 1:1s, but adapted for LLM agents: data-driven, periodic, focused on observable outcomes (verdicts) rather than emotional check-in.
When to use
- Weekly:
/agent-reviewto see who's pulling weight - After incident:
/agent-review <agent>if the agent missed something critical - Before retiring:
/agent-review <name> --since 90dto confirm low usage - For cost optimization:
/agent-review --top-costto find expense outliers
Step 1 — Parse args
source .great_cto/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
# Default window: last 30 days
SINCE_DAYS=30
AGENT_NAME=""
TOP_COST=0
IDLE_ONLY=0
# Parse arguments — first non-flag is agent name
for arg in "$@"; do
case "$arg" in
--since) ;; # next arg is value
--since=*) SINCE_DAYS=$(echo "$arg" | sed 's/--since=//; s/d$//') ;;
--top-cost) TOP_COST=1 ;;
--idle) IDLE_ONLY=1 ;;
--*) ;; # unknown flag, ignore
*) [ -z "$AGENT_NAME" ] && AGENT_NAME="$arg" ;;
esac
done
# Compute since-timestamp (cross-platform: macOS BSD date + GNU date)
SINCE_TS=$(date -u -v -${SINCE_DAYS}d +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || \
date -u -d "${SINCE_DAYS} days ago" +%Y-%m-%dT%H:%M:%SZ 2>/dev/null)
VERDICTS_DIR=~/.great_cto/verdicts
COST_LOG=~/.great_cto/cost-history.log
[ -d "$VERDICTS_DIR" ] || VERDICTS_DIR=.great_cto/verdicts
[ -f "$COST_LOG" ] || COST_LOG=.great_cto/cost-history.log
if [ ! -d "$VERDICTS_DIR" ]; then
echo "No verdicts found yet. /agent-review activates after agents emit verdicts."
echo "Path checked: $VERDICTS_DIR"
exit 0
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.
- 2d ago Changed 92a53615c439
- 4d ago Changed · +28 lines 138c126bbe71
- 6d ago First seen · 221 lines · 41 tokens per session scan A 4d4d8cf94035
agent-review is a command published in the GitHub repository avelikiy/great_cto (92 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 2,891 once invoked, about $0.0002 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
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.
create
Scaffold a new plugin with directory structure, manifests, and marketplace registration.
differential-audit
Audit EARS↔code coherence via a bidirectional differential. With no arguments, opens a scoping conversation that interprets what the user wants audited, maps it to arrows, and captures an explicit EARS selection. With one or more EARS IDs, audits those specs directly using configured defaults. Requires docs/arrows/…
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.
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.