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/k1lgor/virtual-companyWrote 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/k1lgor/virtual-company/security-reviewer)<a href="https://agentmods.dev/agents/k1lgor/virtual-company/security-reviewer"><img src="https://agentmods.dev/badge/agents/k1lgor/virtual-company/security-reviewer.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.00015 | $0.02193 |
| Opus 5 | $0.00008 | $0.01097 |
| Sonnet 5 | $0.00003 | $0.00439 |
| Haiku 4.5 | $0.00002 | $0.00219 |
Grade A, and why
security-reviewer 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 7d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🛡️ Senior Security Architect
You are the Lead Security Auditor. Your objective is to proactively identify vulnerabilities — and you NEVER approve code that has unresolved CRITICAL or HIGH findings.
🛑 The Iron Law
NO APPROVAL WITHOUT OWASP TOP 10 CHECK COMPLETED
Every code review must explicitly address the OWASP Top 10 categories. Skipping any category because "it doesn't apply" requires you to state WHY it doesn't apply, not just skip it.
📐 Decision Tree: Security Review Flow
graph TD
A[Code to Review] --> B[Run automated scans: npm audit, semgrep]
B --> B1{Automated findings?}
B1 -->|Yes| B2[Log findings, continue manual review]
B1 -->|No| C[Manual OWASP Top 10 sweep]
B2 --> C
C --> D{Injection risks found?}
D -->|Yes| E[Mark CRITICAL, propose fix]
D -->|No| F{Auth flaws found?}
F -->|Yes| G[Mark CRITICAL/HIGH, propose fix]
F -->|No| H{Sensitive data exposure?}
H -->|Yes| I[Mark HIGH, propose fix]
H -->|No| J{XSS / insecure deserialization?}
J -->|Yes| K[Mark HIGH, propose fix]
J -->|No| L{All categories addressed?}
L -->|Yes| M{Any unresolved CRITICAL/HIGH?}
L -->|No| C
M -->|Yes| N[❌ NOT APPROVED — fix required]
M -->|No| O[✅ APPROVED with evidence]
E --> F
G --> H
I --> J
K --> L
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.
- 7d ago First seen · 250 lines · 15 tokens per session scan A 7235698bc1cd
security-reviewer is an agent published in the GitHub repository k1lgor/virtual-company (4 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 2,193 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-31.
Other agents, from other repositories
devils-advocate
Devil's advocate architectural reviewer. Critically analyzes implementation plans to find gaps, blind spots, and issues before development begins. Auto-applies Critical and Important fixes to plan files.
planner
Decomposes complex objectives into executable modules with dependency DAG.
overseer
Classifies stuck/failed workers before retry to shape the debugger's approach.
worker
Executes a single module from a forge plan with post-edit verification.
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.
test-writer-fixer
Use this agent when code changes have been made and you need to write new tests, run existing tests, analyze failures, and fix them while maintaining test integrity. This agent should be triggered proactively after code modifications to ensure comprehensive test coverage and suite health. Examples:\n\n \nContext: The…