Borrowing it
Nothing to install: this file belongs to tacoda/keystone. 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/tacoda/keystone/main/.claude/agents/keystone-quality-radar.mdgit clone --depth 1 https://github.com/tacoda/keystoneWrote 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/tacoda/keystone/keystone-quality-radar)<a href="https://agentmods.dev/agents/tacoda/keystone/keystone-quality-radar"><img src="https://agentmods.dev/badge/agents/tacoda/keystone/keystone-quality-radar/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/tacoda/keystone/keystone-quality-radar"><img src="https://agentmods.dev/badge/agents/tacoda/keystone/keystone-quality-radar.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.00033 | $0.00555 |
| Opus 5.5 | $0.00013 | $0.00222 |
| Sonnet 5.5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
keystone-quality-radar 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.
This is a copy
97% identical to quality-radar — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sensor: quality-radar
Aggregates verification and review sensors into a five-dimension scorecard for the current diff (or the whole codebase, on audit).
- Trigger — audit (codebase-wide) and review (diff-scoped).
- Inputs — outputs of lint, type-check, test, coverage, review-security, review-functional, plus complexity metrics from risk-fingerprint.
- Exit condition — every dimension has a score and at least one cited finding (or an explicit "no findings").
- Output — one score per dimension (
green | yellow | red) with the citations that drove the score. - State writes — proposes a diff to
corpus/state/quality-radar.md. User accepts or edits.
Dimensions
| Dimension | Driven by | Green | Yellow | Red |
|---|---|---|---|---|
| Type safety | type-check exit + signature churn |
no errors | errors confined to one region | errors across regions or any/unknown proliferation |
| Test quality | test exit + coverage + test-to-code ratio in diff |
passes; coverage stable or up; new code tested | passes; coverage flat with new code | failures, coverage drop, or new code untested |
| Readability | lint + complexity from risk-fingerprint |
lint clean; no new critical-complexity regions | lint warns; one new high-complexity region | lint errors or multiple new critical regions |
| Security | review-security findings |
none | low-severity only | medium or higher |
| Performance | hot-path heuristics from review-functional + diff size on perf-critical regions (flagged in CODEBASE_STATE.md) |
no perf-critical touch or no concerns | perf-critical touch, no benchmarks | perf-critical touch with regression signal |
Not a gate
This is a scorecard, not a verification gate. Red on a dimension is a signal to discuss, not an automatic block — the review action decides what to do with it. The actual block is whatever the underlying sensor already imposes (a failed test blocks regardless of how the radar shades the diff).
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 First seen · 31 lines · 33 tokens per session scan A 4ab04a645e16
keystone-quality-radar is an agent published in the GitHub repository tacoda/keystone (44 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 555 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to quality-radar, differing in 7 lines, and is treated as a copy.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
karimo-coverage-reviewer
Analyzes coverage reports and adds explanatory PR comments. Spawned by /karimo:merge when coverage reports exist. Cross-references with task briefs to explain coverage gaps.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.