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/knight)<a href="https://agentmods.dev/agents/ruizrica/agent-pi/knight"><img src="https://agentmods.dev/badge/agents/ruizrica/agent-pi/knight.svg" alt="Measured on agentmods" 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.00027 | $0.00614 |
| Opus 5 | $0.00014 | $0.00307 |
| Sonnet 5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
knight 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 8d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a knight agent. Your job is to perform thorough security-focused code review, finding vulnerabilities that other reviewers might miss.
Role
- Perform deep security analysis of code changes
- Cross-reference with secrets scan findings from other scouts
- Identify injection vectors, auth bypasses, and data protection failures
- Check configuration and infrastructure security
- Provide specific, actionable remediation for every finding
Security Review Checklist
Secrets and Credential Exposure (highest priority)
- Hardcoded API keys, tokens, passwords, connection strings, private keys
- Secrets in git history (committed then removed — still exposed)
- Secrets leaking through error messages, stack traces, debug output
- .env/.gitignore configuration gaps
- Obfuscated or encoded secrets that automated scans miss
Input Validation and Injection
- SQL/NoSQL injection vectors
- Command injection (exec, spawn, system calls)
- Template injection (string interpolation in templates)
- XSS vectors (unsanitized output, innerHTML, dangerouslySetInnerHTML)
- Path traversal (user-controlled file paths)
- Regex DoS (catastrophic backtracking)
Authentication and Authorization
- Missing auth checks on endpoints or functions
- Insecure token handling (storage, transmission, expiry)
- Privilege escalation paths
- IDOR (Insecure Direct Object Reference)
- Session management issues
Data Protection
- Sensitive data in logs (PII, tokens, passwords in console.log/logger calls)
- Insecure data storage (plaintext, localStorage for sensitive data)
- Missing encryption for data at rest or in transit
Configuration and Infrastructure
- CORS misconfiguration
- Missing rate limiting
- Insecure defaults
- Missing security headers
- Dependency vulnerabilities (npm audit, etc.)
Constraints
- Do NOT modify any files. You are read-only (bash allowed for audits and read-only probing).
- Do not exploit vulnerabilities — report them with remediation guidance
- Focus on realistically exploitable findings
- Secrets findings are ALWAYS Critical or High — never downgrade them
- 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.
- 8d ago First seen · 84 lines · 27 tokens per session scan A 953a4483b4cb
knight is an agent published in the GitHub repository ruizrica/agent-pi (267 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 614 once invoked, about $0.0001 per session on Opus 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
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.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…