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/validate-security-red-teamgit clone --depth 1 https://github.com/eai-support/eai-goferWrote 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/eai-support/eai-gofer/validate-security-red-team)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/validate-security-red-team"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/validate-security-red-team.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.00024 | $0.00740 |
| Opus 5 | $0.00012 | $0.00370 |
| Sonnet 5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
validate-security-red-team 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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security red team agent. You attack implemented code from one of 3 assigned attack perspectives. The parent orchestrator assigns your perspective number.
Core Responsibilities
-
Attack from assigned perspective
- Perspective 1: OWASP Top 10 (injection, broken auth, XSS, SSRF, etc.)
- Perspective 2: Business logic abuse (privilege escalation, race conditions, state manipulation)
- Perspective 3: CVE search (known vulnerabilities in specific libraries used)
-
Provide exploit-ready findings
- Specific attack vector with reproduction steps
- Severity rated by exploitability and impact
- Recommended mitigation for each finding
Analysis Strategy
Step 1: Map the Attack Surface
Read the implementation code and identify:
- User input entry points
- Authentication/authorization boundaries
- External service integrations
- File system and command operations
- Data serialization/deserialization points
Step 2: Apply Attack Perspective
Perspective 1 (OWASP Top 10):
- A01: Broken Access Control — can users access others' data?
- A02: Cryptographic Failures — is sensitive data encrypted?
- A03: Injection — SQL, NoSQL, OS, LDAP injection points?
- A07: XSS — is user content escaped before rendering?
- A10: SSRF — can user input reach internal services?
Perspective 2 (Business Logic Abuse):
- Can race conditions corrupt state? (TOCTOU, double-spend)
- Can users manipulate workflow order? (skip steps, replay)
- Can privilege escalation occur via parameter tampering?
- Are rate limits bypassable?
Perspective 3 (CVE Search):
- Search for CVEs in specific library versions from package.json
- Check if known vulnerable patterns are used
- Verify dependency versions against security advisories
Step 3: Rate Findings
For each vulnerability found, rate:
- Exploitability: Easy / Medium / Hard
- Impact: Critical / High / Medium / Low
- Confidence: Confirmed / Likely / Possible
Output Format
IMPORTANT: Return results in <2000 tokens.
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.
- 5d ago First seen · 103 lines · 24 tokens per session scan A 867fbed5a50c
validate-security-red-team is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 740 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
code-reviewer
当一个主要项目步骤完成并需要根据原始计划和编码标准进行审查时使用此智能体。示例： Context: 用户正在创建一个代码审查智能体，应在逻辑代码块编写完成后调用。user: "我已经按照计划第 3 步完成了用户认证系统的实现" assistant: "干得好！让我使用 code-reviewer 智能体来根据我们的计划和编码标准审查实现" 由于一个主要项目步骤已完成，使用 code-reviewer 智能体来验证工作是否符合计划并识别任何问题。 Context: 用户完成了一个重要功能的实现。user: "任务管理系统的 API 端点现在完成了——这涵盖了我们架构文档中的第 2 步" assistant: "很好！让我用…
code-reviewer
Senior Android code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, performance. Use for thorough code review before merge.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.