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 debugger-driven-analysisgit 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/debugger-driven-analysis)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/debugger-driven-analysis"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/debugger-driven-analysis/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/debugger-driven-analysis"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/debugger-driven-analysis.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.00041 | $0.00524 |
| Opus 5.5 | $0.00016 | $0.00210 |
| Sonnet 5.5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
debugger-driven-analysis 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 1mo 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
Debugger-Driven Analysis
Use runtime evidence to resolve questions that static analysis cannot answer cleanly: unpacking, argument decoding, branch conditions, environment checks, IPC, crypto state, and anti-analysis behavior.
Workflow
- Start from a concrete question, not "debug everything."
- Choose the debugger mode:
- x64dbg for Windows user-mode binaries
- WinDbg for deeper Windows/system scenarios
- pwndbg-like workflows for low-level register/stack discipline
- Set a minimal breakpoint plan:
- process entry / unpacking point
- suspicious imported APIs
- target functions identified in static recon
- memory write / allocation pivots when needed
- Capture:
- arguments and calling convention state
- register snapshots before/after call
- buffers, decoded strings, and memory changes
- control-flow decisions at critical branches
- Feed confirmed runtime facts back into static naming, signatures, and comments.
Tool Families to Prefer
binary_analysis_*x64dbg*binary_analysis_*windbg*binary_analysis_*session*binary_analysis_*report*
If the exact prefixed names are unclear, use discover_tools with x64dbg debugger winDbg reverse engineering.
Debugger Heuristics
- Break on semantic pivots, not every instruction.
- Snapshot before patching or forcing branches.
- Record the minimum evidence needed to answer the current hypothesis.
- Correlate every important dynamic observation to a static function or address.
Deliverable Format
- Question being tested
- Breakpoints and why they were chosen
- Runtime observations
- Static addresses/functions updated from those observations
- Recommended next action
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.
- 1mo ago First seen · 63 lines · 41 tokens per session scan A 826cb08a5796
debugger-driven-analysis is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 524 once invoked, about $0.0002 per session on Opus 5.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
evidence-audit
Evidence-led audit/fix rounds for any codebase in any language. Finds only defects that a runnable proof reproduces on current code, applies the narrowest in-scope patch, verifies with a second proof, promotes high-risk proofs to permanent regression tests, and reports exact validation results. Use whenever the user…
bug-hunter
Use this skill when scanning source code for bugs, anti-patterns, code smells, or quality issues in a codebase, or when running a proof-driven bug hunt that must find, prove, fix, and verify one real defect. Trigger on the explicit vocabulary — "bug", "bug hunt", "/bughunt", "scan for issues", "find problems"…
debugging
Use this skill when something is broken and the cause is unknown — a failing test, a crash, an error message, wrong output, a regression, a hang, or behaviour that differs between environments — and it has to be found and fixed at the root. Also use it to build the failing proof for a suspected defect before fixing…
observability
Use this skill when adding or reviewing logging, metrics, or tracing in an application, or when a production problem can't be diagnosed from the signals that exist today. Triggers: user says "logging", "logs", "trace", "tracing", "metrics", "observability", "instrument", "OpenTelemetry", "structured logging", "log…
container-debugging
Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
incident-response
Diagnose and recover an owned service incident with bounded changes, timeline evidence and verified health. Use during outages, bad deployments or data/service degradation; preserve evidence and separate mitigation from root-cause repair.