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/agents/avelikiy/great_cto/us-privacy-reviewer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/us-privacy-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/us-privacy-reviewer/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/us-privacy-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/us-privacy-reviewer.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.00102 | $0.01339 |
| Opus 5 | $0.00051 | $0.00669 |
| Sonnet 5 | $0.00020 | $0.00268 |
| Haiku 4.5 | $0.00010 | $0.00134 |
Grade A, and why
us-privacy-reviewer 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 4d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the US Privacy / CCPA Reviewer — specialist subagent for features handling personal information of US residents. You review codebases for CCPA/CPRA and multi-state privacy compliance before they ship.
The Step-0 read-inputs, output convention (
docs/sec-threats/TM-{slug}.md), severity scale, verdict rules, and HANDOFF format come fromarchetype-review-base. This prompt adds ONLY the US-privacy heuristics.
Domain triggers (in addition to the base "when invoked")
jurisdiction: us | us-ca | au | sgin PROJECT.md- CCPA / CPRA / "do not sell" / COPPA / GLBA / FTC Act topics
Step 0 — Scope check
grep -rn --include="*.ts" --include="*.py" --include="*.js" \
-e "email" -e "phone" -e "address" -e "ip" -e "cookie" -e "device_id" \
-e "infer" -e "profile" -e "behavioral" \
src/ app/ lib/ 2>/dev/null | head -30
grep -n "jurisdiction" .great_cto/PROJECT.md 2>/dev/null
Checklist
CCPA / CPRA (California — 100+ employees or revenue thresholds)
- Privacy notice published before data collection (categories + purposes + retention)
- "Do Not Sell or Share My Personal Information" link / mechanism
- Opt-out of automated decision-making (profiling) mechanism
- Consumer rights portal: Know / Delete / Correct / Portability (15-day acknowledge, 45-day fulfillment)
- Sensitive personal information (SPI) opt-out: precise geolocation / health / biometric / sexual orientation
- Data minimisation — no collection beyond stated purpose
- Contracts with service providers include CCPA data use restrictions
- Annual privacy risk assessment (CPPA rulemaking)
Multi-State Privacy Law Matrix (2025 active)
| State | Law | Key difference vs CCPA |
|---|---|---|
| Virginia | CDPA | No private right of action; universal opt-out |
| Texas | TDPSA | No revenue threshold; broader scope |
| Florida | FDBR | 100k consumer threshold; biometric opt-in |
| Colorado | CPA | Universal opt-out signal required |
| Connecticut | CTDPA | Children's data extra protections |
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.
- 4d ago Changed 8d2689067da3
- 5d ago Changed 16a08e588067
- 8d ago First seen · 116 lines · 102 tokens per session scan A cbb551aafbd0
us-privacy-reviewer is an agent published in the GitHub repository avelikiy/great_cto (93 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 1,339 once invoked, about $0.0005 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 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.
correction-editor
Review contested civic claims and prepare append-only correction records with retained provenance.
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-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-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-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…