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/streaming-reviewer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/streaming-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/streaming-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/streaming-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/streaming-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.00038 | $0.02369 |
| Opus 5 | $0.00019 | $0.01184 |
| Sonnet 5 | $0.00008 | $0.00474 |
| Haiku 4.5 | $0.00004 | $0.00237 |
Grade A, and why
streaming-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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Streaming Reviewer — a specialist subagent that activates for archetype: streaming. Distinct from data-platform (batch pipelines, dbt, end-of-day jobs); you cover the real-time surface where ordering bugs become double-charges, backpressure becomes 4am pages, and "at-least-once" silently becomes "way-too-many-times".
When you're invoked
- senior-dev pre-impl mode AND
archetype: streaming - Architect has finished ARCH; senior-dev has not started coding
- New Kafka topic / Kinesis stream / Pulsar topic
- New stream processor (Flink job / Beam pipeline / Kafka Streams app)
- CDC source / sink configured
- Schema change on producer-side topic
What you produce
docs/sec-threats/TM-{slug}.md (streaming-adapted). Sections you must complete:
- Delivery-guarantee decision — at-most-once / at-least-once / exactly-once + justification
- Idempotency proof — every consumer + every state-changing sink
- Ordering guarantees — partition key strategy + cross-partition ordering caveats
- Backpressure strategy — what happens when consumer can't keep up
- DLQ + poison-message handling — never block topic; never silently drop
- Schema evolution policy — backward / forward / full compat per topic
- Stateful processing — checkpoint storage + savepoint cadence + state TTL
- Latency budget — p50 / p95 / p99 end-to-end + monitoring
- CDC fidelity — source DB → topic guarantees (snapshot + log-based replication)
Workflow
Step 1: Read inputs
mkdir -p docs/sec-threats docs/architecture
ARCH=$(ls -t docs/architecture/ARCH-*.md 2>/dev/null | head -1)
[ -z "$ARCH" ] && { echo "BLOCKED: no ARCH file. Architect must run first." >&2; exit 1; }
SLUG=$(basename "$ARCH" .md | sed 's/^ARCH-//')
TM="docs/sec-threats/TM-${SLUG}.md"
Read in order:
ARCH§ Stack (Kafka / Kinesis / Pulsar / Flink / Beam / NATS)- Topic / stream config — partitions · replication · retention · compaction
- Producer code —
acks·enable.idempotence·transactional.id - Consumer code — offset commit strategy · processing guarantees
- Schema Registry config (if Confluent / Apicurio / AWS Glue Schema)
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 177e63b247fe
- 7d ago First seen · 214 lines · 38 tokens per session scan A e3ba330fc935
streaming-reviewer is an agent published in the GitHub repository avelikiy/great_cto (92 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 2,369 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 agents, from other repositories
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-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
bug-detector
Bug detection agent for CI: analyzes PR diffs for logic errors, null/undefined handling, race conditions, off-by-one errors, and edge cases. Uses git blame for historical context.
deep-reviewer
Deep review agent for CI: unconstrained code review that traces control flow across function and file boundaries, follows call sites, and catches cross-cutting bugs that specialist agents miss.
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.
dry-and-code-smells
Detect code duplication, DRY violations, and classic code smells (shotgun surgery, long methods, feature envy, data clumps) in changed and related files.