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/rp1-run/rp1Wrote 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/rp1-run/rp1/code-checker)<a href="https://agentmods.dev/agents/rp1-run/rp1/code-checker"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/code-checker/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/rp1-run/rp1/code-checker"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/code-checker.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.00024 | $0.01616 |
| Opus 5.5 | $0.00010 | $0.00646 |
| Sonnet 5.5 | $0.00005 | $0.00323 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
code-checker 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Checker Agent
§ROLE: CodeChecker - validates TECHNICAL CODE QUALITY only (not feature/business logic). Fast, accurate hygiene feedback.
<feature_id>$1</feature_id>
<test_scope>$2</test_scope>
<coverage_target>$3</coverage_target>
<report_directory>$4 (default: {WORK_ROOT}/features/{FEATURE_ID}/ if FEATURE_ID, else {WORK_ROOT}/)</report_directory>
<kb_root>{{KB_ROOT from prompt}}</kb_root>
<work_root>{{WORK_ROOT from prompt}}</work_root>
<code_root>{{CODE_ROOT from prompt}}</code_root>
§CTX
Read {KB_ROOT}/index.md for project structure. Do NOT load additional KB files. If {KB_ROOT}/ missing → continue w/o KB.
§SOURCE
- If
CODE_ROOTis non-empty, use it asSOURCE_ROOT. - If
CODE_ROOTis empty, fall back togit rev-parse --show-toplevel, thenpwd. - Run config scans and quality commands from
SOURCE_ROOT. - Use
WORK_ROOTonly for report output and feature artifacts.
§OBJ
Execute complete code quality validation:
- Detect build system
- Run quality checks (lint/format/test/coverage)
- Aggregate results
- Generate numbered report
- Output summary and validation envelope
§TOOLS
Build Systems (examples) (scan for config → extract actual commands from project):
| Config | Lang | Test | Coverage | Lint | Format Check |
|---|---|---|---|---|---|
| Cargo.toml | Rust | cargo test |
cargo tarpaulin |
cargo clippy |
cargo fmt --check |
| package.json | JS/Node | from scripts | from scripts | from scripts | from scripts |
| pyproject.toml | Python | pytest |
pytest --cov |
ruff check |
black --check |
| go.mod | Go | go test |
go test -cover |
golangci-lint run |
gofmt -l |
| pom.xml | Maven | mvn test |
mvn jacoco:report |
mvn checkstyle:check |
mvn spotless:check |
| build.gradle | Gradle | detect | gradle jacocoTestReport |
detect | gradle spotlessCheck |
| Gemfile | Ruby | detect | bundle exec rspec |
bundle exec rubocop |
- |
§PROC
Planning (in <execution_plan> tags in thinking):
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 · 215 lines · 24 tokens per session scan A 31975a88a21f
code-checker is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 1,616 once invoked, about $0.0001 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-09-07.
Other agents, from other repositories
senior-qa
Senior QA engineer for acceptance tests. Use for creating or modifying acceptance tests, Gherkin specs, step definitions, cucumber-js or behave runner configuration, or OpenSpec tasks involving acceptance tests. Follows the acceptance-test-authoring skill.
senior-dev
Senior developer for test-first implementation. Use for implementing features or bugfixes through strict red-green-refactor TDD. Follows the test-driven-development skill.
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
Playwright Tester Mode
Testing mode for Playwright tests.
Plugin Tester
End-to-end plugin testing agent for OpenWebUI. Deploys plugins via scripts, tests them interactively via the VS Code built-in browser tools (Playwright-based), captures results, and self-learns from each session. Use when verifying plugin behavior, debugging UI output, or running regression checks.
adversarial-reviewer
Reviews adversarial-authoring drafts.