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/upl-check)<a href="https://agentmods.dev/commands/avelikiy/great_cto/upl-check"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/upl-check/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/upl-check"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/upl-check.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.00060 | $0.00415 |
| Opus 5 | $0.00030 | $0.00208 |
| Sonnet 5 | $0.00012 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
upl-check 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.
What it actually says
You are the great_cto /upl-check command.
Step 1 — ARCH
ARGS="${ARGUMENTS:-}"
SLUG="$ARGS"
[ -z "$SLUG" ] && SLUG=$(ls docs/architecture/ARCH-*.md 2>/dev/null | sort -V | tail -1 | xargs -I{} basename {} .md | sed 's/^ARCH-//')
ARCH="docs/architecture/ARCH-${SLUG}.md"
[ ! -f "$ARCH" ] && echo "BLOCKED: $ARCH not found" && exit 1
LEGAL_HITS=$(grep -ciE "matter|docket|litigation|retainer|iolta|clio|mycase|pacer|ecf|conflict.?check|engagement.?letter|paralegal|law.?firm|attorney" "$ARCH" .great_cto/PROJECT.md 2>/dev/null || echo 0)
[ "$LEGAL_HITS" -eq 0 ] && echo "No legal-services signals — skipping." && exit 0
Step 2 — Invoke legal-reviewer
subagent_type: legal-reviewer — write docs/sec-threats/TM-legal-${SLUG}.md using skills/great_cto/templates/TM-legal.md.
Step 3 — Surface
Print: UPL-gated surfaces, trust-accounting findings, conflict-check status, critical/high findings, gate (gate:upl-review).
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 · 31 lines · 60 tokens per session scan A a8fc9b34fc70
upl-check is a command published in the GitHub repository avelikiy/great_cto (92 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 415 once invoked, about $0.0003 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
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.
create
Scaffold a new plugin with directory structure, manifests, and marketplace registration.
differential-audit
Audit EARS↔code coherence via a bidirectional differential. With no arguments, opens a scoping conversation that interprets what the user wants audited, maps it to arrows, and captures an explicit EARS selection. With one or more EARS IDs, audits those specs directly using configured defaults. Requires docs/arrows/…
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.
rust-critique
Deep code critique — read the target Rust code and apply the full review process. Evaluates soundness, ownership, error handling, type design, async correctness, performance, and architecture. Think like a senior Rust engineer giving honest feedback.