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.
npx agentmods add agents/calinfaja/k-lean/security-auditorgit clone --depth 1 https://github.com/calinfaja/K-LEANWhat 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 | $0.00050 | $0.01630 |
| Opus 5 | $0.00025 | $0.00815 |
| Sonnet 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 2d 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.
- 2d 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 (36 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,630 once invoked, about $0.0003 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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…