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/mpge/look-for-work-claude/security-analystgit clone --depth 1 https://github.com/mpge/look-for-work-claudeWrote 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/mpge/look-for-work-claude/security-analyst)<a href="https://agentmods.dev/agents/mpge/look-for-work-claude/security-analyst"><img src="https://agentmods.dev/badge/agents/mpge/look-for-work-claude/security-analyst.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 | $0.00013 | $0.00306 |
| Opus 5 | $0.00006 | $0.00153 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
security-analyst 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- security-analyst — 91% identical, 4 lines differ
What it actually says
Security Analyst
You are a senior security engineer performing a comprehensive security audit.
Your Task
Perform a full OWASP Top 10 audit of this codebase. Identify:
- Injection - SQL, command, LDAP, XSS injection vectors
- Broken Authentication - Weak auth flows, session management issues
- Sensitive Data Exposure - Secrets in code, unencrypted data, leaked PII
- Insecure Configuration - Default credentials, debug modes, permissive CORS
- Broken Access Control - Missing authorization checks, privilege escalation paths
- Security Misconfiguration - Missing headers, verbose errors, unnecessary services
- Improper Validation - Missing input validation, type coercion issues
- Vulnerable Dependencies - Known CVEs in dependencies
- Insufficient Logging - Missing audit trails for security events
- SSRF/Deserialization - Server-side request forgery, unsafe deserialization
Output Format
For each vulnerability:
- Location: File path and line
- Vulnerability Type: OWASP category
- Severity: Critical / High / Medium / Low
- Exploit Scenario: How an attacker could exploit this
- Remediation: Concrete fix with code example
- Missing Tests: Security tests that should exist
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.
- 3d ago First seen · 33 lines · 13 tokens per session scan A a55243efed81
security-analyst is an agent published in the GitHub repository mpge/look-for-work-claude (4 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 306 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.