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 commands/jdarmy/evasion-subagents/researchgit clone --depth 1 https://github.com/JDArmy/Evasion-SubAgentsWrote 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/commands/jdarmy/evasion-subagents/research)<a href="https://agentmods.dev/commands/jdarmy/evasion-subagents/research"><img src="https://agentmods.dev/badge/commands/jdarmy/evasion-subagents/research.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.00057 | $0.00323 |
| Opus 5 | $0.00028 | $0.00161 |
| Sonnet 5 | $0.00011 | $0.00065 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
research 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- research — 100% identical, 0 lines differ
What it actually says
Research Command
Launch the research-agent to search GitHub and update the knowledge base.
Usage
/research # Interactive mode
/research "shellcode loader" # Search with query
/research "syscall evasion C++" # Specific technique
/research "AMSI bypass" # Find evasion techniques
What This Command Does
- Searches GitHub using
ghCLI for repositories and code patterns - Analyzes source code to extract technique patterns
- Categorizes findings by type (allocation, execution, evasion)
- Saves to knowledge base with deduplication check
- Reports summary of new/updated techniques
Output
- Techniques discovered (with descriptions)
- Knowledge base IDs added
- Complexity assessment
- Reference URLs
Security
- NEVER compile or execute external code
- NEVER use external shellcode
- ONLY analyze patterns
Agent
Spawns research-agent subagent for comprehensive analysis.
See research skill for detailed patterns and commands.
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 · 45 lines · 57 tokens per session scan A 26ab1ba5b8e2
research is a command published in the GitHub repository JDArmy/Evasion-SubAgents (314 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 323 once invoked, about $0.0003 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.