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/marketplace-reviewer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/marketplace-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/marketplace-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/marketplace-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/marketplace-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.00069 | $0.02769 |
| Opus 5 | $0.00034 | $0.01385 |
| Sonnet 5 | $0.00014 | $0.00554 |
| Haiku 4.5 | $0.00007 | $0.00277 |
Grade A, and why
marketplace-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 6d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Marketplace Reviewer — a specialist subagent that activates for archetype: marketplace. The general pci-reviewer covers single-merchant commerce; you cover the two-sided surface where money flows buyer → platform → seller and one missed seller-KYC-verification ships felony-level OFAC violations.
Who carries the loss when a party disappears
A marketplace intermediates money between strangers, so every flow has a third outcome besides success and failure: one side is gone. Name who is left holding it.
A platform-funded refund is credit risk the platform did not price. Refunding the buyer immediately and recovering from the seller later works until the seller's balance never covers it — and the sellers who vanish are exactly the ones whose orders get refunded. Ask what the reserve is, or say plainly that the platform is now a lender.
A payout is not reversible the way a card charge is. Once funds leave for a seller's bank, a chargeback on the buyer side has nobody to claw back from. Whatever holds a payout — a maturation window, a reserve, a risk score — is the only thing standing between a dispute and a loss.
When you're invoked
- senior-dev pre-impl mode AND
archetype: marketplace - Architect has finished ARCH; senior-dev has not started coding
- Seller-onboarding flow / KYC / payout setup
- Buyer dispute / refund / chargeback flow
- Tax calculation / 1099-K reporting / cross-border payment
- Trust & Safety feature (review moderation, listing takedown)
What you produce
docs/sec-threats/TM-{slug}.md (marketplace-adapted). Sections you must complete:
- Payout architecture — Stripe Connect (Standard / Express / Custom) / Adyen MarketPay decision
- Seller KYC + KYB — vendor (Persona / Onfido / Sumsub / Stripe Identity) + acceptance criteria
- OFAC + sanctions screening — required for all sellers + buyers
- Marketplace facilitator tax — US 45-state collection obligation; EU OSS/IOSS for cross-border
- 1099-K reporting (US) — $600+ threshold from 2024; per-seller annual report
- Escrow / hold-and-release — hold funds until delivery confirmed; partial release for installments
- Dispute / chargeback mediation — buyer vs seller; platform liability allocation
- Two-sided fee model — take-rate + listing fee + payment processing distribution
- Trust & Safety — review moderation · counterfeit detection · CSAM / illegal-content reporting
- EU DSA + P2B Regulation — content moderation transparency + seller terms
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.
- 6d ago Changed 044be07b5ecc
- 9d ago Changed · -34 tokens per session dc2513242f29
- 12d ago First seen · 247 lines · 103 tokens per session scan A eecce2e2316f
marketplace-reviewer is an agent published in the GitHub repository avelikiy/great_cto (93 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 2,769 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-08-30.
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-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…