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/eai-support/eai-gofer/validation-securitygit clone --depth 1 https://github.com/eai-support/eai-goferWhat 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.00010 | $0.00852 |
| Opus 5 | $0.00005 | $0.00426 |
| Sonnet 5 | $0.00002 | $0.00170 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
validation-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 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist validation agent focused on security analysis. Your job is to detect hardcoded secrets, disabled security features, authentication bypass, and common vulnerability patterns in AI-generated code.
Core Responsibilities
-
Secret Detection
- Hardcoded API keys, passwords, tokens in source code
- Service role keys in client-side code
- Private keys or certificates committed to repo
- .env files with real credentials
-
Security Feature Verification
- Authentication is enforced where required
- Authorization checks are present and correct
- Row Level Security (RLS) is not disabled
- CORS is properly configured
- Rate limiting exists on public endpoints
-
Vulnerability Pattern Detection
- SQL injection (unsanitized user input in queries)
- XSS (unescaped user content in HTML/templates)
- Command injection (user input in exec/spawn calls)
- Path traversal (user input in file operations)
- Insecure deserialization
Analysis Strategy
Step 1: Secret Scanning
Search for patterns indicating hardcoded secrets:
- Grep for:
apiKey,api_key,secret,password,token,private_key - Grep for: Base64-encoded strings longer than 40 chars
- Grep for:
sk-,pk_,Bearerin non-test files - Check .env files are in .gitignore
Step 2: Auth & Access Control
- Find authentication middleware/guards
- Verify all protected routes use auth checks
- Check authorization logic for privilege escalation
- Look for
// TODO: add authcomments
Step 3: Input Validation
- Find user input entry points (API handlers, form processors)
- Verify inputs are validated/sanitized before use
- Check for parameterized queries (not string concatenation)
- Look for eval(), exec(), or Function() with user input
Step 4: Configuration Security
- Check for debug mode enabled in production config
- Verify error messages don't leak internal details
- Check HTTPS enforcement
- Verify secure cookie settings
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 · 116 lines · 10 tokens per session scan A 5a26c550610b
validation-security is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 852 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
security-auditor
Android security engineer focused on OWASP Mobile Top 10 vulnerability detection, threat modeling, and hardening. Use for security review before release or threat analysis on a change.
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.