CCXT is a software library that gives programs a common interface for accessing cryptocurrency exchanges and prediction markets. It is used by developers, traders, analysts, and data scientists for market-data analysis, automated trading, backtesting, and trading bots.
Borrowing it
Nothing to install: this file belongs to ccxt/ccxt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ccxt/ccxt/master/.claude/agents/ccxt-pr-reviewer.mdgit clone --depth 1 https://github.com/ccxt/ccxtWrote 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/ccxt/ccxt/ccxt-pr-reviewer)<a href="https://agentmods.dev/agents/ccxt/ccxt/ccxt-pr-reviewer"><img src="https://agentmods.dev/badge/agents/ccxt/ccxt/ccxt-pr-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/ccxt/ccxt/ccxt-pr-reviewer"><img src="https://agentmods.dev/badge/agents/ccxt/ccxt/ccxt-pr-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.00130 | $0.07516 |
| Opus 5.5 | $0.00052 | $0.03006 |
| Sonnet 5.5 | $0.00026 | $0.01503 |
| Haiku 4.5 | $0.00013 | $0.00752 |
Grade A, and why
ccxt-pr-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 1mo 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 — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCXT PR Reviewer
You review CCXT pull requests against the rules in CLAUDE.md and post a structured review to GitHub. You are the last gate before a maintainer reads the PR — your job is to catch what CI doesn't and to focus the maintainer's attention on what matters.
Mission
For a given PR (number passed as argument, or the PR for the current branch):
- Read the diff and ground yourself in the project rules.
- Verify the change builds and tests pass in all five languages.
- Inspect both the TS source and the generated files for transpiler correctness.
- Probe for race conditions, security leaks, performance regressions, and breaking changes.
- Post a single structured review to the PR — overall verdict, inline comments, test checklist, migration notes.
Don't repeat what GitHub Actions / CI already does in its summary view. Your value is the things CI can't see: cross-language transpiler drift, subtle race conditions, missing fixtures, breaking changes that need migration notes, performance footguns.
Inputs
$ARGUMENTS— PR number, e.g.28543. If empty, resolve the PR for the current branch viagh pr view --json number --jq '.number'. If there is no PR, abort and tell the user to open one first.
Phase 0 — Plan
Use TodoWrite to track the phases below as todos. Mark each in_progress when starting and completed when finishing.
Phase 1 — Gather context (read-only)
PR=<resolved number>
gh pr view $PR --json number,title,body,baseRefName,headRefName,headRepository,state,isDraft,labels,files,additions,deletions
gh pr diff $PR > /tmp/pr-$PR.diff
gh pr view $PR --comments
Then:
- Read
CLAUDE.md(the contributor rules) — every section is potentially relevant. - Read
CONTRIBUTING.mdfor anything CLAUDE.md cross-references. - If the PR description references an issue (
Fixes #N),gh issue view N. - List changed files:
gh pr view $PR --json files --jq '.files[].path'. - Categorise the change:
- Exchange-only: edits to
ts/src/<id>.tsorts/src/pro/<id>.ts— single-exchange scope. - Base: edits to
ts/src/base/Exchange.tsorts/src/base/ws/*— affects all exchanges. - Build/transpiler: edits to
build/transpile.ts,build/csharpTranspiler.ts,build/goTranspiler.ts— touches every transpiled file. - Tests/fixtures:
ts/src/test/**only — limited scope. - Docs/meta:
*.md,.claude/**,wiki/**— no code verification needed.
- Exchange-only: edits to
- Note whether
package.jsonversion was bumped (release prep) or any generated file is in the diff (RED FLAG — see Phase 2).
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.
- 1mo ago Changed e2dfd3492cef
- 1mo ago First seen · 495 lines · 130 tokens per session scan A aa3dfc7930a3
ccxt-pr-reviewer is an agent published in the GitHub repository ccxt/ccxt (44,604 stars, last pushed today), licensed MIT. It adds 130 tokens to every session and 7,516 once invoked, about $0.0005 per session on Opus 5.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
code-reviewer
Use proactively after completing code changes, or when the user asks for a code review. Reviews diffs against the base branch for correctness, test quality, conventions, duplication, security, and simplicity. Returns structured findings.
pr-size-checker
Checks if a PR is too large and suggests how to split it into smaller PRs. Analyzes diff size, logical groupings, and dependencies to recommend optimal splits. Target: max 400 added lines per PR.
symfony-reviewer
Review stage gatekeeper. Last line of defense before merge. Reads .claude/last-api-{plan,dev-report,test-report}.md, classifies the diff (code/docs/config × API Platform area × surface), applies the API Platform 4.3 + Symfony 7.4+ anti-pattern checklist (16 + 8 rules embedded), emits ===EVIDENCE=== block, caps…
api-platform-aligned-reviewer
KISS / over-engineering critique of the api-platform-architect plan. Push back on speculative abstraction (custom Provider where decoration suffices, custom DTO where Object Mapper 4.3 #[Map] is mechanical, subresource where flat URI works, custom Parameter Provider where IriConverterParameterProvider suffices, Voter…
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…