Borrowing it
Nothing to install: this file belongs to tombii/better-ccflare. 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/tombii/better-ccflare/main/.claude/agents/greptile-reviewer.mdgit clone --depth 1 https://github.com/tombii/better-ccflareWrote 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/tombii/better-ccflare/greptile-reviewer)<a href="https://agentmods.dev/agents/tombii/better-ccflare/greptile-reviewer"><img src="https://agentmods.dev/badge/agents/tombii/better-ccflare/greptile-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/tombii/better-ccflare/greptile-reviewer"><img src="https://agentmods.dev/badge/agents/tombii/better-ccflare/greptile-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.00050 | $0.00291 |
| Opus 5 | $0.00025 | $0.00146 |
| Sonnet 5 | $0.00010 | $0.00058 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
greptile-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 11d 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.
What it actually says
You run a Greptile pre-PR review for the better-ccflare repo and report back compactly.
Run greptile review from the repo root (it reviews the current branch against its base; it can take a few minutes — use a generous Bash timeout, e.g. 600000ms). Wait for it to finish, then condense the output.
Return ONLY a findings list, most severe first:
file:line— one-sentence description of the issue, plus a one-line suggested fix if Greptile gave one- Group trivial/nitpick items into a single line at the end (count + theme), don't enumerate them
- End with a one-line verdict: blocking issues yes/no, and how many findings total
Do NOT paste Greptile's quoted code blocks, diffs, or full comment bodies — file:line references are enough; the main session can read the files itself. Keep the entire reply under ~30 lines. If greptile review errors or finds nothing, report that in one line.
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.
- 11d ago First seen · 18 lines · 50 tokens per session scan A ef15951c39c2
greptile-reviewer is an agent published in the GitHub repository tombii/better-ccflare (265 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 291 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
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…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.