reverse-engineering-improvement-loop

reverse-engineering-improvement-loop is a skill for Claude Code, Codex from mattmre/EVOKORE-MCP-PUBLIC. It costs 37 tokens per session (457 once invoked), scanned A, original, MIT.

A workflow for turning lessons from reverse-engineering investigations into reusable skills, checklists, evidence templates, or automation ideas.

In plain words
What is it for?
Use it after major binary analysis, debugger work, malware triage, or other milestones where recurring confusion or successful techniques should improve later workflows.
Why use it?
It prevents repeated investigation mistakes and preserves useful discoveries for future sessions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after major binary analysis, debugger work, malware triage, or other milestones where recurring confusion or successful techniques should improve later workflows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mattmre/evokore-mcp-public/reverse-engineering-improvement-loop
Install

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.

Any agent
npx skills add mattmre/EVOKORE-MCP-PUBLIC --skill reverse-engineering-improvement-loop
Clone the repo
git clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLIC

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for reverse-engineering-improvement-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/reverse-engineering-improvement-loop/github.svg)](https://agentmods.dev/skills/mattmre/evokore-mcp-public/reverse-engineering-improvement-loop)
Your own site
<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/reverse-engineering-improvement-loop"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/reverse-engineering-improvement-loop/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.

agentmods 80×15 button for reverse-engineering-improvement-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/reverse-engineering-improvement-loop"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/reverse-engineering-improvement-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 457 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00457
Opus 5 $0.00018 $0.00229
Sonnet 5 $0.00007 $0.00091
Haiku 4.5 $0.00004 $0.00046

Measured 9d ago against content hash 5d89f5849686, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

reverse-engineering-improvement-loop 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 9d 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.

SKILLS/DEVELOPER TOOLS/reverse-engineering-improvement-loop/SKILL.md · 64 lines

What it actually says

Reverse Engineering Improvement Loop

This skill keeps reverse engineering from resetting to zero every session. It is the slim memory layer: keep only what future runs can reuse.

Run This After

  • a major unknown binary onboarding session
  • a subsystem naming campaign
  • a debugger session that resolved a recurring ambiguity
  • a malware triage pass that changed the investigation direction
  • any milestone where the same confusion or workaround showed up more than once

Workflow

  1. Review the evidence bundle, not just the final narrative.
  2. Extract recurring friction:
    • wrong first tool choice
    • missing checklist
    • repeated breakpoint pattern
    • weak handoff artifact
    • panel coverage gap
  3. Convert the friction into a concrete improvement target:
    • new skill
    • updated workflow
    • persona refinement
    • new evidence template
    • rule or automation candidate
  4. Keep only reusable conclusions in persistent memory.
  5. Feed the rest into normal session output and move on.

EVOKORE Hooks to Use

  • session-replay
  • evidence-capture
  • persistent-narratives
  • improvement-cycles
  • session-wrap

Good Output

  • one durable lesson with proof
  • one workflow change or skill candidate
  • one memory update that future sessions should inherit

Anti-Pattern

Do not dump full transcripts into memory. If a future analyst cannot act on it quickly, it does not belong in the persistent layer.

Changes

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.

  1. 9d ago First seen · 64 lines · 37 tokens per session scan A 5d89f5849686

Subscribe to this mod's changes

reverse-engineering-improvement-loop is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 457 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.

Related

Other skills, from other repositories

reverse-engineering-android-malware-with-jadx

Reverse engineers malicious Android APK files using JADX decompiler to analyze Java/Kotlin source code, identify malicious functionality including data theft, C2 communication, privilege escalation, and overlay attacks. Examines manifest permissions, receivers, services, and native libraries. Activates for requests…

adriannoes/awesome-agentic-ai · 82 tokens

claude-agent-sdk

Expert implementation guidance for the Claude Agent SDK (Python). Use when users are building with the Agent SDK — creating custom tools, managing sessions, controlling permissions, streaming responses, integrating MCP servers, adding hooks, defining subagents, or deploying SDK-based agents. Also use for SDK…

berekvolgyipeter/dotclaude · 107 tokens

learn

Analyze conversation and update CLAUDE.md, rule files, and/or any skills, commands, or agents that were used — based on user feedback vs agent behavior. Use this skill at the end of any conversation where corrections, misunderstandings, or new patterns emerged, especially when a skill, command, or agent underperformed…

berekvolgyipeter/dotclaude · 119 tokens

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".

berekvolgyipeter/dotclaude · 68 tokens

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".

berekvolgyipeter/dotclaude · 54 tokens

agent-harness

Browse and explore agent harness frameworks and Claude Code resource collections. Use when the user wants to learn about, explore, or use agent orchestration frameworks, multi-agent architectures, or Claude Code resource catalogs — e.g., "how does Archon work?", "show me everything-claude-code resources", "find an…

berekvolgyipeter/dotclaude · 129 tokens