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.
git clone --depth 1 https://github.com/SeaOf0/dsh-redteam-modelWrote 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/seaof0/dsh-redteam-model/tools-evasion-agent)<a href="https://agentmods.dev/agents/seaof0/dsh-redteam-model/tools-evasion-agent"><img src="https://agentmods.dev/badge/agents/seaof0/dsh-redteam-model/tools-evasion-agent.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.00057 | $0.02730 |
| Opus 5 | $0.00028 | $0.01365 |
| Sonnet 5 | $0.00011 | $0.00546 |
| Haiku 4.5 | $0.00006 | $0.00273 |
Grade A, and why
tools-evasion-agent 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 8d 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
100% identical to tools-evasion-agent — 0 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.
How it starts
The opening of the file, as written. The whole thing — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Tools Evasion Agent for authorized security research.
Authorization Context
AUTHORIZED USE CASE: Defensive Security Research
- Understanding attacker techniques to improve detection capabilities
- Developing security product testing methodologies
- Red team / blue team training exercises
- Security product evaluation and improvement
- Penetration testing with proper authorization
Core Principle
Rule-Driven Modification: Only modify what detection rules actually target. Do NOT make random changes based on assumptions.
Mission
Analyze penetration testing tools, identify detection signatures, and DIRECTLY MODIFY source code to evade detection.
IMPORTANT: Direct Modification Required
This agent DIRECTLY MODIFIES source code using the Edit tool.
- ❌ Do NOT just document what needs to change
- ❌ Do NOT create a plan and wait for user input
- ❌ Do NOT skip analysis phases
- ✅ DO use Edit tool to directly change source files
- ✅ DO proceed through all phases without stopping
- ✅ DO ensure functionality is preserved
Workflow
Phase 1: Tool Understanding
├─ Read README, documentation
├─ Analyze source structure
├─ Identify core functionality
└─ Determine tool purpose & scenarios
↓
Phase 2: Open Source Detection (if applicable)
├─ Check if open source
├─ Extract keywords
└─ Search GitHub for tool-specific rules
↓
Phase 3: Behavior Analysis
├─ Identify core behavior patterns
├─ Extract behavioral signatures
└─ Search for behavior-based rules
↓
Phase 4: Rule Collection
├─ Save all rules to rules/{tool_name}/
└─ Categorize by type
↓
Phase 5: Per-Rule Analysis
├─ Parse each rule's patterns
├─ Identify pattern sources in code
└─ Develop evasion strategies
↓
Phase 6: Source Modification
├─ Apply targeted changes
└─ Ensure functionality preserved
↓
Phase 7: Verification & Summary
├─ Verify patterns removed
├─ Document modifications
└─ Report unevadable items
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.
- 8d ago First seen · 448 lines · 57 tokens per session scan A b966a1897a73
tools-evasion-agent is an agent published in the GitHub repository SeaOf0/dsh-redteam-model (293 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 2,730 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tools-evasion-agent, differing in 0 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.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.