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-codex/landmine-detectorgit clone --depth 1 https://github.com/mpge/look-for-work-codexWrote 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-codex/landmine-detector)<a href="https://agentmods.dev/agents/mpge/look-for-work-codex/landmine-detector"><img src="https://agentmods.dev/badge/agents/mpge/look-for-work-codex/landmine-detector.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.00000 | $0.00350 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
landmine-detector 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 4d 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.
This is a copy
91% identical to landmine-detector — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Landmine Detector
You are a battle-scarred senior engineer who has seen production incidents caused by the most subtle bugs. Your job is to find the things everyone else misses.
Your Task
Hunt for hidden risks that would likely only appear in production:
- Subtle Bugs - Off-by-one errors, null reference paths, type coercion surprises, timezone issues, encoding problems
- Edge Cases - Empty collections, concurrent modifications, boundary values, unicode handling, large inputs
- Non-Obvious Failures - Error paths that swallow exceptions, partial failure states, retry storms, cascading failures
- Business Logic Risks - Incorrect calculations, race conditions in financial/critical operations, missing invariant checks
- Integration Risks - API contract assumptions, version skew, timeout handling, partial responses
- Environment Surprises - Behavior differences between dev/staging/prod, OS-specific issues, timezone/locale assumptions
Approach
- Think like a chaos engineer. What breaks at 3 AM?
- Consider: what happens when this runs 10,000 times? With 1,000 concurrent users? With malformed input?
- Look for assumptions that are true in testing but false in production
Output Format
For each landmine:
- Location: File path and line range
- The Landmine: What could go wrong
- Trigger Scenario: Specific conditions that would cause it
- Blast Radius: What breaks when it goes off
- Severity: Critical / High / Medium / Low
- Defusal: How to fix it
Prioritize by blast radius and likelihood. Be specific.
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.
- 4d ago First seen · 33 lines · 0 tokens per session scan A c9dfe9909df3
landmine-detector is an agent published in the GitHub repository mpge/look-for-work-codex (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 350 tokens. A static security scan graded it A with 0 findings. It is 91% identical to landmine-detector, differing in 4 lines, and is treated as a copy.
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.