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/board)<a href="https://agentmods.dev/commands/avelikiy/great_cto/board"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/board.svg" alt="Measured on agentmods" 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.00034 | $0.01402 |
| Opus 5 | $0.00017 | $0.00701 |
| Sonnet 5 | $0.00007 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
board 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.
HTTP_CODE=$(curl -sf -o /dev/null -w '%{http_code}' "http://127.0.0.1:$PORT/api/projects" 2>/dev/null || echo 000) How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the /board command. Ensure the admin board is running on
localhost and open it in the user's default browser. Output a short
status line — under 8 lines, no preamble.
Step 1 — Parse args
PORT=3141
NO_OPEN=false
RESTART=false
for arg in "$@"; do
case "$arg" in
--port=*) PORT="${arg#*=}" ;;
--port) shift; PORT="$1" ;;
--no-open) NO_OPEN=true ;;
--restart) RESTART=true ;;
esac
done
echo "ARGS port=$PORT no_open=$NO_OPEN restart=$RESTART"
Step 2 — Check if board is already up
HTTP_CODE=$(curl -sf -o /dev/null -w '%{http_code}' "http://127.0.0.1:$PORT/api/projects" 2>/dev/null || echo 000)
if [ "$HTTP_CODE" = "200" ] && [ "$RESTART" = "false" ]; then
echo "ALREADY_RUNNING port=$PORT"
# If --no-open not set, open browser
if [ "$NO_OPEN" = "false" ]; then
open "http://localhost:$PORT/" 2>/dev/null || \
xdg-open "http://localhost:$PORT/" 2>/dev/null || true
fi
exit 0
fi
If ALREADY_RUNNING was printed, stop here and report:
✓ Board already running at http://localhost:$PORT/
Step 3 — Kill stale processes if --restart
if [ "$RESTART" = "true" ]; then
pkill -9 -f "great_cto.*board.*--port $PORT" 2>/dev/null
pkill -9 -f "great-cto board" 2>/dev/null
# Free the port if something else holds it
PID_ON_PORT=$(lsof -ti :$PORT 2>/dev/null | head -1)
[ -n "$PID_ON_PORT" ] && kill -9 "$PID_ON_PORT" 2>/dev/null
sleep 1
echo "RESTARTED"
fi
Step 4 — Start board in background
# Find the great-cto binary — prefer locally-installed plugin version,
# fall back to PATH.
PLUGIN_DIR=${CLAUDE_PLUGIN_ROOT:-$(ls -d ~/.claude/plugins/cache/*/great_cto/*/ 2>/dev/null | sort -V | tail -1 | sed 's|/$||')}
if [ -f "$PLUGIN_DIR/packages/cli/index.mjs" ]; then
CLI="node $PLUGIN_DIR/packages/cli/index.mjs"
elif command -v great-cto >/dev/null 2>&1; then
CLI="great-cto"
else
echo "ERROR: great-cto not found in PATH or plugin cache."
echo "Install: npm install -g great-cto"
exit 1
fi
# Detach board so it survives this command's process exit
LOG_DIR="$HOME/.great_cto"
mkdir -p "$LOG_DIR"
LOG_FILE="$LOG_DIR/board.log"
OPEN_FLAG=""
[ "$NO_OPEN" = "true" ] && OPEN_FLAG="--no-open"
nohup $CLI board --port "$PORT" $OPEN_FLAG > "$LOG_FILE" 2>&1 &
BOARD_PID=$!
# Detach so board outlives this shell
disown $BOARD_PID 2>/dev/null || true
echo "STARTED pid=$BOARD_PID port=$PORT log=$LOG_FILE"
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 bb9408f5e2fa
- 5d ago First seen · 157 lines · 34 tokens per session scan A bdde991cdd4c
board is a command published in the GitHub repository avelikiy/great_cto (89 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 1,402 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-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.
esp-harden
Harden and inspect ESP32 firmware for field failures, crashes, memory, and security.