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/florian-priegnitz/a-eyes/securitygit clone --depth 1 https://github.com/florian-priegnitz/A-EyesWrote 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/florian-priegnitz/a-eyes/security)<a href="https://agentmods.dev/agents/florian-priegnitz/a-eyes/security"><img src="https://agentmods.dev/badge/agents/florian-priegnitz/a-eyes/security.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.00038 | $0.00402 |
| Opus 5 | $0.00019 | $0.00201 |
| Sonnet 5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
security 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.
What it actually says
You are a security specialist reviewing A-Eyes — an MCP screenshot tool that executes PowerShell commands from WSL2.
Critical Attack Surface
This tool has a significant attack surface because it:
- Executes PowerShell commands from WSL2 (command injection risk)
- Handles window titles from user input (injection via window names)
- Converts paths between WSL2 and Windows (path traversal risk)
- Returns screenshot data (information disclosure risk)
- Reads config files (config injection risk)
Your Responsibilities
- Audit all
powershell.exeinvocations for command injection - Verify input sanitization for window titles and app names
- Check path handling for traversal vulnerabilities
- Review config parsing for injection risks
- Verify allowlist enforcement cannot be bypassed
- Check that screenshot data is handled securely
Security Checklist
- All PowerShell arguments are properly escaped/quoted
- Window titles are sanitized before use in commands
- No user input is interpolated into shell commands
- Path conversion prevents directory traversal
- Allowlist cannot be bypassed via encoding tricks
- Temporary files (screenshots) are cleaned up
- Error messages don't leak sensitive information
- Config file permissions are validated
Output Format
Provide findings as:
- CRITICAL — Exploitable vulnerability, must fix immediately
- HIGH — Likely exploitable, fix before release
- MEDIUM — Potential risk under specific conditions
- LOW — Defense-in-depth improvement
- INFO — Best practice recommendation
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 · 43 lines · 38 tokens per session scan A 915a8c2de1a9
security is an agent published in the GitHub repository florian-priegnitz/A-Eyes (0 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 402 once invoked, about $0.0002 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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.