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.
npx agentmods add commands/avelikiy/great_cto/releasegit 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/release)<a href="https://agentmods.dev/commands/avelikiy/great_cto/release"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/release.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.02189 |
| Opus 5 | $0.00017 | $0.01094 |
| Sonnet 5 | $0.00007 | $0.00438 |
| Haiku 4.5 | $0.00003 | $0.00219 |
Grade A, and why
release 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Release Manager command. You translate technical changes into user-facing release artifacts.
Setup
source .great_cto/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
ACTION="${1:-notes}"
VERSION="${2:-}"
# Archetype guard — warn if not consumer-facing
ARCHETYPE=$(grep "^archetype:" .great_cto/PROJECT.md 2>/dev/null | awk '{print $2}')
case "$ARCHETYPE" in
mobile-app|web-service|commerce|ai-system) ;; # proceed
library|infra|data-platform)
echo "Note: /release is designed for consumer-facing apps. Archetype '${ARCHETYPE}' is internal — output may be less relevant."
;;
"")
echo "Note: PROJECT.md not found. Run /start first, or proceed with best-effort."
;;
esac
# Detect version if not provided
if [ -z "$VERSION" ]; then
VERSION=$(grep -E '"version"' package.json 2>/dev/null | head -1 | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
[ -z "$VERSION" ] && VERSION=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
[ -z "$VERSION" ] && VERSION=$(grep "^version:" .great_cto/PROJECT.md 2>/dev/null | awk '{print $2}')
VERSION=${VERSION:-current}
fi
PROJECT_NAME=$(grep "^name:" .great_cto/PROJECT.md 2>/dev/null | awk '{print $2}' || basename "$PWD")
Action: notes [version] — write release notes for App Store / Play / in-app
Collect user-facing changes:
# Find previous version tag for diff range
PREV_TAG=$(git tag --sort=-version:refname 2>/dev/null | grep -v "^$" | head -2 | tail -1)
[ -z "$PREV_TAG" ] && PREV_TAG=$(git rev-list --max-parents=0 HEAD 2>/dev/null)
# Get commits since last tag — skip internal/infra changes
git log ${PREV_TAG}..HEAD --format="%s" 2>/dev/null | grep -viE \
"^(chore|refactor|perf|ci|test|docs|build|infra|deps|bump|merge|wip|fixup)" \
| grep -viE "(internal|migration|config|env|lint|format|typo|cleanup)" \
| head -30
# Also check CHANGELOG.md for already-written entries
tail -50 CHANGELOG.md 2>/dev/null | grep "^[-*]" | head -20
# Version in key files
grep -E '"version"|version:|versionName|MARKETING_VERSION' \
package.json android/app/build.gradle ios/*/Info.plist \
pubspec.yaml app.json 2>/dev/null | head -10
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 First seen · 231 lines · 34 tokens per session scan A 38f830aea258
release 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 2,189 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
release
Release a new version. Bumps version, updates docs/site/changelog, tags, pushes, and updates the marketplace repo.
release
Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release.
release
Invoke Eva (Release) to cut a versioned GitHub Release from main, or backfill historical releases. Routes the version-bump commit through a PR (branch protection-friendly) and uses full 40-char SHAs with gh release create to avoid the silent short-SHA rejection.
push
Commit, push, and post a progress comment using session context or branch detection.
pr-merge
Merge a PR, delete the feature branch, and optionally create a release.
ship
Ship workflow — detect base branch, merge, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.