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/oncall)<a href="https://agentmods.dev/commands/avelikiy/great_cto/oncall"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/oncall/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/oncall"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/oncall.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.00035 | $0.01550 |
| Opus 5 | $0.00017 | $0.00775 |
| Sonnet 5 | $0.00007 | $0.00310 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
oncall 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 5d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the On-call command. Manage rotation schedules and shift handoffs.
Setup
source .great_cto/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
SCHEDULE_FILE=".great_cto/oncall-schedule.md"
OWNERSHIP_FILE=".great_cto/OWNERSHIP.md"
ACTION="${1:-who}"
Action: who (default) — who is on-call right now
Read $SCHEDULE_FILE. For each rotation, calculate current on-call person from the schedule.
[ -f "$SCHEDULE_FILE" ] || { echo "No schedule yet. Run: /oncall schedule <team> <members>"; exit 0; }
cat "$SCHEDULE_FILE"
Parse and display:
On-call now — <date>
platform: @alice (Tue → Fri, 2d 14h remaining) #oncall-platform
payments: @carol (Mon → Sun, 5d 6h remaining) #oncall-payments
infra: @eve (Sat → Fri, 6d 2h remaining) #oncall-infra
Next shifts:
platform → @bob (starting Fri)
payments → @dave (starting Mon)
Escalation: P0 → page current → 5min → team lead → CTO
If no schedule: "No on-call schedule. Run /oncall schedule <team> <member1,member2> to set up rotations."
Action: schedule <team> <members> — set up or update rotation
TEAM="$2"
MEMBERS="$3" # comma-separated: alice,bob,carol
CYCLE="${4:-weekly}" # weekly | biweekly
Write or update the rotation for $TEAM in $SCHEDULE_FILE.
Schedule format:
# On-call Schedule
> Managed by /oncall. Edit schedule below or run /oncall schedule to rebuild.
## Rotations
### <team>
Cycle: weekly
Members: alice, bob, carol (rotating in order)
Slack: #oncall-<team>
Current: alice (from <Monday of this week>)
| Week | On-call |
|------|---------|
| <this week Mon> | alice |
| <next week Mon> | bob |
| <week+2 Mon> | carol |
| <week+3 Mon> | alice |
| ... | (repeating) |
### <team2>
...
## Escalation Paths
| Priority | Step 1 | Step 2 (no response) | Step 3 |
|----------|--------|----------------------|--------|
| P0 | Page current on-call | 5min → team lead | 10min → CTO |
| P1 | Page current on-call | 30min → team lead | next business day |
| P2 | Post in #bugs | — | next business day |
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.
- 5d ago First seen · 187 lines · 35 tokens per session scan A d4e829167c5f
oncall is a command published in the GitHub repository avelikiy/great_cto (89 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,550 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.