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 skills add mattmre/EVOKORE-MCP-PUBLIC --skill malware-triage-workflowgit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/skills/mattmre/evokore-mcp-public/malware-triage-workflow)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/malware-triage-workflow"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/malware-triage-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/malware-triage-workflow"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/malware-triage-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.00513 |
| Opus 5 | $0.00024 | $0.00257 |
| Sonnet 5 | $0.00010 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
malware-triage-workflow 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 11d 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
Malware Triage Workflow
Run a behavior-first triage that quickly answers what the sample touches, how risky it looks, and which routines deserve deep reverse engineering.
Workflow
- Collect static indicators first:
- format, architecture, packer or entropy clues
- imports, exports, strings, sections, resources
- suspicious APIs and network / filesystem / registry markers
- YARA or family-pattern matches if available
- Identify high-risk behavior buckets:
- persistence
- credential access
- command and control
- injection / hollowing
- crypto / ransomware behavior
- anti-analysis / sandbox checks
- Select a small set of target functions for deeper decompilation.
- Use debugger confirmation only for the riskiest unknowns:
- decoded config
- runtime-resolved imports
- dropped paths
- beacon construction
- key material or encryption flow
- Produce a short operator report before moving into full family-level RE.
Tool Families to Prefer
binary_analysis_*triage*binary_analysis_*malware*binary_analysis_*yara*binary_analysis_*control*binary_analysis_*report*ghidra_headless_search.*ghidra_headless_reference.*ghidra_headless_decomp.function
Output Structure
- Sample identity and format summary
- Top suspicious indicators
- Likely behavior categories
- Priority functions / addresses for deeper RE
- Dynamic checks still required
- Confidence level and major unknowns
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.
- 11d ago First seen · 63 lines · 49 tokens per session scan A 60fcf065501c
malware-triage-workflow is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 513 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 skills, from other repositories
deobfuscating-powershell-obfuscated-malware
Systematically deobfuscate multi-layer PowerShell malware using AST analysis, dynamic tracing, and tools like PSDecode and PowerDecode to reveal hidden payloads and C2 infrastructure.
investigating-ransomware-attack-artifacts
Identify, collect, and analyze ransomware attack artifacts to determine the variant, initial access vector, encryption scope, and recovery options.
ts-debug
TypeScript/Node debugging expert. Use when the user needs to debug, profile, or trace TypeScript or Node.js code — e.g. "how do I debug this", "find the memory leak", "why is this slow", "add a breakpoint", "profile this function", "why won't the process exit".
py-debug
Python debugging expert. Use when the user needs to debug, profile, or trace Python code — e.g. "how do I debug this", "find the memory leak", "why is this slow", "add a breakpoint", "profile this function".
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware using Ghidra with specialized scripts for function recovery, string extraction, and type reconstruction in stripped Go binaries.
deep-analysis
Performs focused, depth-first investigation of specific reverse engineering questions through iterative analysis and database improvement. Answers questions like "What does this function do?", "Does this use crypto?", "What's the C2 address?", "Fix types in this function". Makes incremental improvements (renaming…