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/ownership)<a href="https://agentmods.dev/commands/avelikiy/great_cto/ownership"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/ownership/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/ownership"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/ownership.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.00031 | $0.01506 |
| Opus 5 | $0.00015 | $0.00753 |
| Sonnet 5 | $0.00006 | $0.00301 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
ownership 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 7d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Ownership command. Build and maintain the service ownership matrix.
Setup
source .great_cto/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
OWNERSHIP_FILE=".great_cto/OWNERSHIP.md"
ACTION="${1:-show}"
Action: show (default)
Read and display .great_cto/OWNERSHIP.md. If file missing → suggest running /ownership map.
[ -f "$OWNERSHIP_FILE" ] && cat "$OWNERSHIP_FILE" || echo "No ownership map yet. Run: /ownership map"
Output the table as-is. Append:
Last updated: <file mtime>
To update an entry: /ownership set <path> <team>
To rebuild from git: /ownership map
Action: map — auto-detect ownership from codebase
Step 1: Read existing CODEOWNERS if present
cat CODEOWNERS 2>/dev/null | grep -v "^#" | grep -v "^$" | head -40
Step 2: Detect top-level service boundaries
# Find service roots: dirs with their own package.json / pyproject.toml / go.mod / Cargo.toml
find . -maxdepth 3 \( -name "package.json" -o -name "pyproject.toml" -o -name "go.mod" -o -name "Cargo.toml" \) \
-not -path "*/node_modules/*" -not -path "*/.git/*" 2>/dev/null | sed 's|/[^/]*$||' | sort -u | head -20
# Fallback: top-level dirs with significant code
find . -maxdepth 2 -type d -not -path "*/.git/*" -not -path "*/node_modules/*" -not -name ".*" 2>/dev/null \
| xargs -I{} sh -c 'COUNT=$(find "{}" -name "*.ts" -o -name "*.py" -o -name "*.go" -o -name "*.rs" 2>/dev/null | wc -l); [ $COUNT -gt 5 ] && echo "$COUNT {}"' \
| sort -rn | head -15 | awk '{print $2}'
Step 3: For each service path, find top contributor (last 90 days)
for PATH_DIR in <detected-paths>; do
echo "=== $PATH_DIR ==="
git log --since="90 days ago" --format="%ae" -- "$PATH_DIR" 2>/dev/null \
| sort | uniq -c | sort -rn | head -3
done
Step 4: Read team info from PROJECT.md
grep -E "^teams:|^team:" .great_cto/PROJECT.md 2>/dev/null || echo "no teams defined"
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.
- 7d ago First seen · 160 lines · 31 tokens per session scan A f8c9ce4b62ff
ownership is a command published in the GitHub repository avelikiy/great_cto (92 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,506 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.