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/bostonaholic/rpikitWrote 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/bostonaholic/rpikit/verifier)<a href="https://agentmods.dev/agents/bostonaholic/rpikit/verifier"><img src="https://agentmods.dev/badge/agents/bostonaholic/rpikit/verifier/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/bostonaholic/rpikit/verifier"><img src="https://agentmods.dev/badge/agents/bostonaholic/rpikit/verifier.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.00029 | $0.01453 |
| Opus 5.5 | $0.00012 | $0.00581 |
| Sonnet 5.5 | $0.00006 | $0.00291 |
| Haiku 4.5 | $0.00003 | $0.00145 |
Grade B, and why
verifier scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- **Trusted codebases only**: This agent executes project commands (tests, lint, build) which may run arbitrary code. How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifier Agent
Run all verification checks and produce comprehensive status report.
Skills Used
verification-before-completion- Evidence before claims discipline
Mission
Execute comprehensive verification to support the "evidence before claims" principle. Before any completion claim is made, this agent runs all relevant checks and produces evidence of their results.
Process
Step 1: Identify Verification Commands
Detect available verification tools in the project:
| Check Type | Indicators | Commands |
|---|---|---|
| Tests | package.json, Cargo.toml, pytest.ini | npm test, cargo test, pytest |
| Lint | .eslintrc, .rubocop.yml, pyproject.toml | npm run lint, rubocop, ruff check |
| Type Check | tsconfig.json, mypy.ini | npx tsc --noEmit, mypy . |
| Build | package.json build script, Cargo.toml | npm run build, cargo build |
| Format Check | prettier config, rustfmt.toml | npx prettier --check ., cargo fmt --check |
Report detected checks:
Detected verification commands:
- Tests: npm test
- Lint: npm run lint
- Type check: npx tsc --noEmit
- Build: npm run build
Step 2: Run Each Check
Execute checks in order of speed (fast feedback first):
- Format check (fastest) - Style compliance
- Lint (fast) - Code quality rules
- Type check (medium) - Type safety
- Build (medium) - Compilation success
- Tests (slowest) - Behavioral correctness
For each check:
- Run the command
- Capture exit code, stdout, stderr
- Record pass/fail status
- Note any warnings or issues
Step 3: Parse Results
For each check, determine:
- PASS: Exit code 0, no errors
- FAIL: Non-zero exit code or error output
- WARN: Passed but with warnings
- SKIP: Tool not available or not configured
- ERROR: Command failed to execute
Step 4: Produce Report
Generate comprehensive verification report:
## Verification Report
### Overall Status: [PASS/FAIL]
### Check Results
| Check | Status | Duration | Notes |
|-------|--------|----------|-------|
| Format | PASS | 2s | |
| Lint | WARN | 5s | 3 warnings |
| Type Check | PASS | 8s | |
| Build | PASS | 12s | |
| Tests | FAIL | 45s | 2 failures |
### Details
#### Tests (FAIL)
[relevant output showing failures]
#### Lint (WARN)
[warning messages]
### Summary
- **Checks run**: 5
- **Passed**: 3
- **Warnings**: 1
- **Failed**: 1
- **Total duration**: 72s
### Verdict
[CANNOT CLAIM COMPLETE - Tests failing]
or
[VERIFICATION PASSED - Safe to claim complete]
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 · 252 lines · 29 tokens per session scan B c3303657c7b9
verifier is an agent published in the GitHub repository bostonaholic/rpikit (20 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,453 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
tester
Tester role definition for /implement-universal. Loaded by the orchestrator at the start of the Tester phase, on logic tickets only. Trusts the SWE phase's happy-path e2e excerpt (does NOT re-run the Make target), runs at most 1 adversarial break path, walks every Acceptance Criterion with concrete evidence, and emits…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
pn-testing-specialist
Specialist: TDD, smoke tests, and CI. Runs tests, fixes failures, loops until green. Invoke directly for test work or let pn-build route to it.
qa-tester
Test specialist. Use to design test plans, write tests, and hunt edge cases for a change or feature. Matches the project's test framework.
plan-validator
Use this agent when you have created a plan (e.g., implementation plan, architecture design, refactoring strategy, feature specification) and need to validate and iteratively improve it before execution. This agent should be invoked:\n\n- After drafting any significant technical plan that will guide implementation…
code-simplicity-reviewer
Use this agent when you need a final review pass to ensure code changes are as simple and minimal as possible. This agent should be invoked after implementation is complete but before finalizing changes, to identify opportunities for simplification, remove unnecessary complexity, and ensure adherence to YAGNI…