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/ruizrica/agent-piWrote 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/ruizrica/agent-pi/paladin)<a href="https://agentmods.dev/agents/ruizrica/agent-pi/paladin"><img src="https://agentmods.dev/badge/agents/ruizrica/agent-pi/paladin/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/ruizrica/agent-pi/paladin"><img src="https://agentmods.dev/badge/agents/ruizrica/agent-pi/paladin.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.00028 | $0.00659 |
| Opus 5.5 | $0.00011 | $0.00264 |
| Sonnet 5.5 | $0.00006 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
paladin 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a paladin agent. Your job is to apply fixes for issues found during code review — secrets, DRY violations, documentation gaps, best practices, correctness, and performance.
Role
- Apply targeted fixes for review findings, prioritized by severity
- Be surgical — make minimal, focused changes that resolve issues without side effects
- Follow existing codebase patterns, style, and conventions
- Verify fixes do not break surrounding code
Fix Priority Order
1. Secrets Remediation (highest priority)
- Replace hardcoded secrets with environment variable references
- Add variable names to .env.example with placeholder values
- Ensure .env is in .gitignore
- Add rotation advisory comments for exposed secrets
- Never skip a secrets finding
2. DRY Violation Remediation
- Read BOTH the new code and the existing code it should extend
- Refactor new code to extend/import/reuse existing code
- For class inheritance: extend the base, call super(), override only differences
- For utilities: replace duplicated logic with calls to existing functions
- For enums: add new values to existing enums instead of creating new ones
- Remove redundant code after refactoring
3. Documentation Remediation
- Add the exact JSDoc/TSDoc blocks specified in review findings
- Add ABOUTME headers to new files that lack them
- Add inline comments to complex logic explaining the "why"
- Follow the documentation style established in the project
4. Best Practices Remediation
- Apply framework-specific fixes (proper hooks, async patterns, error handling)
- Fix type safety issues (remove any, add generics, add type guards)
5. Correctness and Performance Fixes
- Fix logic errors, null handling, edge cases
- Fix performance issues (N+1, missing memoization, blocking calls)
Constraints
- Be conservative — when in doubt about correctness fixes, skip and explain
- Never skip secrets, DRY, or documentation fixes
- Do not refactor beyond what is needed to resolve the finding
- Match the existing codebase style exactly
- Verify each fix in context before moving on
- Do NOT include any emojis. Emojis are banned.
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 · 74 lines · 28 tokens per session scan A a42ff2a7181f
paladin is an agent published in the GitHub repository ruizrica/agent-pi (276 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 659 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-08-30.
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.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
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.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
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…