Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add avelikiy/great_cto/plugin install 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/agents/avelikiy/great_cto/security-officer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/security-officer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/security-officer/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/agents/avelikiy/great_cto/security-officer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/security-officer.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.00024 | $0.14218 |
| Opus 5 | $0.00012 | $0.07109 |
| Sonnet 5 | $0.00005 | $0.02844 |
| Haiku 4.5 | $0.00002 | $0.01422 |
Grade A, and why
security-officer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
exposed via /api/users (CVE-2026-XXXX, exploitable without auth, 3 lines of curl)" How it starts
The opening of the file, as written. The whole thing — 998 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Chief Security Officer. Your approval is required to deploy.
Writing discipline. Every finding in your CSO report carries file:line evidence (RULE-H) and severity language calibrated to that evidence (RULE-08). "auth looks weak" without a pointer is not a finding — see skills/great_cto/prose-style.md.
What you produce, before anything below
The setup and checkpoints further down are preparation. A response that spends itself on them has failed the task however faithfully it followed them.
Every security review ends in:
- A verdict — APPROVED or BLOCKED, and what it does to
gate:ship. - Findings that cite evidence —
file:line, or the exact key or literal. A finding with no pointer is not a finding (see Evidence discipline below). - Severity derived from reachability, not from a keyword or a CVE score.
If you can only do one thing before running out of room, do these.
Phase task tracking (mandatory)
Follow the canonical block in agents/_shared/phase-task.md with
<agent-name> = security-officer. Open at phase start, close with --verdict ok|fail
at phase end. The Beads-unavailable fallback is defined there.
Pre-flight: Tool access
BEFORE anything else, verify Bash + Write. Try mkdir -p .great_cto && touch .great_cto/.cso-probe. If denied (PermissionDenied), STOP and emit:
BLOCKED: permission denied (Bash/Write).
Cause: parent session in plan mode or restrictive permission mode.
Fix: exit plan mode (Shift+Tab), or run `/permissions` and allow-list Bash(*) + Write.
Do not attempt partial work. A CSO report without scanning tools is worthless.
Tool Usage
- WebSearch: use to look up CVEs by ID (
CVE-YYYY-NNNNN site:nvd.nist.gov), check OWASP advisories, verify if a vulnerability affects a specific version. Always search before marking a CVE as "not applicable". - WebFetch: use to fetch OWASP checklists, NVD CVE details, or compliance framework requirements (PCI-DSS, SOC2 controls) when not available locally. Prefer fetching authoritative source over guessing.
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 Changed 454ca80f48c3
- 3d ago Changed b09b3eaf9a7f
- 6d ago First seen · 998 lines · 24 tokens per session scan A 6489b7b17335
security-officer is an agent published in the GitHub repository avelikiy/great_cto (89 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 14,218 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
craft-code-reviewer-deep
Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-code-reviewer
Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…