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 HoangNguyen0403/agent-skills-standard --skill cyber-rea-reverse-engineeringgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/cyber-rea-reverse-engineering)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/cyber-rea-reverse-engineering"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/cyber-rea-reverse-engineering/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/hoangnguyen0403/agent-skills-standard/cyber-rea-reverse-engineering"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/cyber-rea-reverse-engineering.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.00062 | $0.01156 |
| Opus 5.5 | $0.00025 | $0.00462 |
| Sonnet 5.5 | $0.00012 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
cyber-rea-reverse-engineering 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cyber REA Reverse Engineering
Priority: P1 (HIGH)
Use REA only when its evidence answers the question; an absent driver blocks one evidence lane, not the task.
Activation
Keywords rea, rea mcp, reverse-engineer-anything, shipped artifact, decompile binary, static javascript analysis, electron app analysis. Skip a complete source repository that already answers the question.
Driver Ladder
- Record authorization: target path, read-only or mutation authority, accountable owner, window, and exclusions.
- Prefer a connected REA MCP whose artifact identity matches the consuming project's recorded source revision and trusted SHA-256. A version string is not identity.
- Otherwise verify and restore the retained bundle into a dedicated
<INSTALL_DIR>, then use itsscripts/rea.mjsthrough the environment-clearing launcher. Setup: references/setup.md. - No REA, unsupported host or Node, unverified identity, or launcher mismatch: analyze supplied files offline with read-only local tools and label the lane
driver: none; do not edit the consumer's MCP config. - Nothing usable: return
BLOCKED (driver: rea)for that lane and continue independent work.
Workflow
- Bind the target to an authorized, operator-supplied local path; never discover targets.
- Preflight the consumer approval record, obtain the trusted manifest SHA-256 out-of-band, verify the bootstrap archive digest before extracting it, run verify and restore with
--manifest-sha256from<TRUSTED_TOOLS>, then launch. Version6.7.0is compatibility metadata, not approval. - Route by target: JavaScript/ASAR -> static application analysis; archive/package -> binary inventory; native code -> configured provider; browser runtime -> separate explicit approval.
- Analyze read-only first. Extraction, patching, execution, injection, install, or any target mutation requires separate explicit authority.
- Record evidence with tool and version, source,
observed_at, target identity or digest when available, findings, limitations, and unknowns. - Keep limitations attached: static analysis is not runtime proof, and a missing provider affects only the operations that need it.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 70 lines · 62 tokens per session scan A c44adc9e4446
cyber-rea-reverse-engineering is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 1,156 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-10-27.
Other skills, from other repositories
perf-optimization
Profile-driven performance optimization protocol. Use when profiling data (CPU, heap, trace) is available or when the user requests performance analysis. Covers methodology (Profile → Analyze → Opportunity Scan → Prioritize → Optimize → Benchmark), optimization pattern catalog, safety invariants, and when-to-stop…
incident-response
Structured incident workflow: severity classification, triage, diagnosis, mitigation, postmortem, and prevention. Template-driven with blameless review.
debug
Structured bug diagnosis and fixing workflow that reproduces, diagnoses root cause, applies a minimal fix, writes regression tests, and scans for similar patterns.
debugging-protocol
Comprehensive protocol for validating root causes of software issues. Use when you need to systematically debug a complex bug, flaky test, or unknown system behavior by forming hypotheses and validating them with specific tasks.
refactor
Safely restructures existing code while preserving behavior through impact analysis and TDD. User-invoked entry point via /refactor; not for autonomous or subagent use.
bugfix
Fixes bugs of any size from hotfixes to complex debugging sessions using root cause diagnosis and TDD. User-invoked entry point via /bugfix; not for autonomous or subagent use.