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-retire)<a href="https://agentmods.dev/commands/avelikiy/great_cto/agent-retire"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/agent-retire/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-retire"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/agent-retire.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.00033 | $0.02327 |
| Opus 5 | $0.00016 | $0.01163 |
| Sonnet 5 | $0.00007 | $0.00465 |
| Haiku 4.5 | $0.00003 | $0.00233 |
Grade A, and why
agent-retire 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Agent Retire command — graceful deprecation flow for AI workforce. Removes an agent from active rotation while preserving audit trail and reversibility.
When to use
- Agent has had 0 invocations in last 90 days (use
/agent-review --idleto find candidates) - Agent's archetype is no longer in your active project mix
- Agent's prompt is being superseded by a better one (consolidation)
- Agent has been flagged as misbehaving in multiple verdicts
What gets retired
- Agent prompt file —
agents/<name>.md→agents/_retired/<name>.md - SessionStart sync list —
<name>removed fromplugin.json - Decisions log — entry added to
~/.great_cto/decisions.md - Verdicts —
~/.great_cto/verdicts/<name>.logpreserved (audit trail; never deleted) - Lessons referencing the agent — left untouched (historical record)
What's reversible
To un-retire: mv agents/_retired/<name>.md agents/<name>.md + add back to sync list. All prior verdicts/lessons resume.
Step 1 — Parse args + validate
source .great_cto/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
ARCHIVE_ONLY=0
REASON=""
AGENT_NAME=""
LIST_CANDIDATES=0
# Parse args
while [ $# -gt 0 ]; do
case "$1" in
--archive-only) ARCHIVE_ONLY=1; shift ;;
--list-candidates) LIST_CANDIDATES=1; shift ;;
--reason) REASON="$2"; shift 2 ;;
--reason=*) REASON="${1#*=}"; shift ;;
*) AGENT_NAME="$1"; shift ;;
esac
done
# --list-candidates mode
if [ "$LIST_CANDIDATES" = "1" ]; then
echo "## Retire candidates — agents with 0 invocations in last 90 days"
echo ""
SINCE_TS=$(date -u -v -90d +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || \
date -u -d "90 days ago" +%Y-%m-%dT%H:%M:%SZ 2>/dev/null)
VERDICTS_DIR=~/.great_cto/verdicts
[ -d "$VERDICTS_DIR" ] || VERDICTS_DIR=.great_cto/verdicts
for log in "$VERDICTS_DIR"/*.log; do
[ -f "$log" ] || continue
AGENT=$(basename "$log" .log)
RECENT_COUNT=$(awk -v ts="$SINCE_TS" '$1 > ts' "$log" | wc -l | tr -d ' ')
if [ "$RECENT_COUNT" = "0" ]; then
LAST=$(tail -1 "$log" 2>/dev/null | awk '{print $1}')
echo "- \`$AGENT\` — last seen $LAST"
fi
done
echo ""
echo "_To retire: \`/agent-retire <name>\`. Files preserved in \`agents/_retired/\` for un-retire later._"
exit 0
fi
# Validate agent name
if [ -z "$AGENT_NAME" ]; then
echo "Usage: /agent-retire <agent-name> [--archive-only] [--reason 'text']"
echo " /agent-retire --list-candidates"
exit 2
fi
AGENT_FILE="agents/$AGENT_NAME.md"
if [ ! -f "$AGENT_FILE" ]; then
echo "No such agent file: $AGENT_FILE"
echo ""
echo "Available agents (active):"
ls agents/*.md 2>/dev/null | sed 's|agents/||; s|\.md||' | head -40
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 · 234 lines · 33 tokens per session scan A fd620d868322
agent-retire is a command published in the GitHub repository avelikiy/great_cto (92 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 2,327 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
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.