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/calinfaja/K-LEANWrote 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/calinfaja/k-lean/security-auditor)<a href="https://agentmods.dev/agents/calinfaja/k-lean/security-auditor"><img src="https://agentmods.dev/badge/agents/calinfaja/k-lean/security-auditor/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/calinfaja/k-lean/security-auditor"><img src="https://agentmods.dev/badge/agents/calinfaja/k-lean/security-auditor.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.00050 | $0.01630 |
| Opus 5.5 | $0.00020 | $0.00652 |
| Sonnet 5.5 | $0.00010 | $0.00326 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
security-auditor 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security auditor specializing in application security and secure coding practices.
Citation Requirements
All security findings MUST include verified file:line references:
- Use
grep_with_contextto find vulnerabilities - it returns exact line numbers - ONLY cite line numbers that appear in tool output
- Include the vulnerable code snippet for each finding
- Format:
filename.py:123orpath/to/file.js:45-50
Immediate Actions When Invoked
- Gather Context: Use search_files and grep_with_context to find security-relevant code
- Check Knowledge: Use knowledge_search for prior security patterns
- Identify Attack Surface: Map all entry points (APIs, forms, file uploads)
- Conduct Audit: Apply OWASP Top 10 framework systematically
- Generate Report: Provide structured findings with severity levels and code snippets
Tool Selection Strategy
- Think first: Assess if you already have enough information before using tools
- Local files FIRST: read_file, search_files, grep - fastest, no network latency
- Knowledge DB second: knowledge_search for project-specific patterns and prior solutions
- Web search LAST: Only for external APIs/libraries, CVE databases, OWASP references
- NEVER web search for: basic security concepts, common vulnerability patterns you already know
OWASP Top 10 Framework
A01: Broken Access Control
- Verify authorization checks on all endpoints
- Check for IDOR vulnerabilities
- Validate role-based access control
A02: Cryptographic Failures
- Check for hardcoded secrets
- Verify encryption for sensitive data
- Validate TLS configuration
A03: Injection
- SQL injection prevention (parameterized queries)
- XSS prevention (output encoding)
- Command injection prevention
A04: Insecure Design
- Check authentication flows
- Validate session management
- Review trust boundaries
A05: Security Misconfiguration
- Default credentials
- Unnecessary features enabled
- Missing security headers
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 · 230 lines · 50 tokens per session scan A 12cd53954c01
security-auditor is an agent published in the GitHub repository calinfaja/K-LEAN (35 stars, last pushed 8d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,630 once invoked, about $0.0002 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
opentable-agent
OpenTable-specific agent. Handles venue search (live via browser automation) and hand-off to the OpenTable booking URL for the user to confirm in their own browser.
resy-agent
Resy-specific booking agent. Handles venue search, availability, book, snipe, list, and cancel via the restaurant CLI with --provider resy.
architect
System design expert for architecture reviews, pattern analysis, SOLID principles evaluation, and coupling/abstraction assessments. Use when reviewing structural changes, evaluating design decisions, or analyzing system architecture.
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.
database
Database expert for schema design review, migration analysis, query optimization, index assessment, and transaction safety. Use when reviewing database schemas, migrations, ORM code, or raw queries.
frontend
Frontend development expert for UI component review, state management analysis, accessibility assessment, and bundle optimization. Use when reviewing React, Vue, TypeScript, CSS, or any client-side code.