Borrowing it
Nothing to install: this file belongs to ricardoquesada/regenerator2000. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ricardoquesada/regenerator2000/main/.agent/skills/compare-unpacker/SKILL.mdgit clone --depth 1 https://github.com/ricardoquesada/regenerator2000Wrote 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/ricardoquesada/regenerator2000/compare-unpacker)<a href="https://agentmods.dev/skills/ricardoquesada/regenerator2000/compare-unpacker"><img src="https://agentmods.dev/badge/skills/ricardoquesada/regenerator2000/compare-unpacker/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/ricardoquesada/regenerator2000/compare-unpacker"><img src="https://agentmods.dev/badge/skills/ricardoquesada/regenerator2000/compare-unpacker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 22 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00043 | $0.01191 |
| Opus 5 | $0.00022 | $0.00596 |
| Sonnet 5 | $0.00009 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
compare-unpacker 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unpacker Comparison Skill (compare-unpacker)
Use this skill when you need to benchmark or compare the Regenerator 2000 unpacker against unp64 across all test PRG binaries registered in test_unpack_known_prg_files.
Single Source of Truth
The single source of truth for test PRG files is test_unpack_known_prg_files in crates/regenerator2000-core/src/unpacker.rs.
The comparison tool (crates/regenerator2000-core/src/bin/unpacker_compare_all.rs) dynamically parses unpacker.rs to extract the exact list of active test PRGs. Do not hardcode the total count of test files in reports or documentation.
Workflow Overview
- Execute Comparison Binary: Run
unpacker_compare_allto execute bothunp64and Regenerator 2000'sunpack()engine on all test files dynamically extracted fromtest_unpack_known_prg_files. - Analyze Output: Extract and compare start address, end address, and entry point for every binary.
- Generate Report Artifact: Create a comprehensive Markdown comparison report summarizing results, exact matches, and categorized discrepancies.
Step 1: Run the Comparison Tool
Execute the comparison binary:
cargo run -p regenerator2000-core --bin unpacker_compare_all
Note: The binary automatically looks for
unp64inPATH,~/.local/bin/unp64,~/bin/unp64, or via theUNP64/UNP64_PATHenvironment variable. Ifunp64is in a custom location, specifyUNP64=/path/to/unp64 cargo run ....
Step 2: Analyze & Categorize Discrepancies
For each file listed by the tool, examine the three primary fields:
- Start Address (
start_addr): Range start address (unp64vsR2000). - End Address (
end_addr): Range end address (unp64vsR2000). - Entry Point (
entry_point): Program entry point address (unp64vsR2000).
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.
- 10d ago First seen · 100 lines · 43 tokens per session scan A 33775b0684ec
compare-unpacker is a skill published in the GitHub repository ricardoquesada/regenerator2000 (164 stars, last pushed 15d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,191 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-30.
Other skills, from other repositories
cartridge-programming
Use when writing, building, or debugging a Commodore 64 cartridge — plain 8K/16K/Ultimax or bank-switched EasyFlash — with the c64 CLI or the c64-tools MCP server. Covers the two boot mechanisms (CBM80 vs the $FFFC reset vector), the memory modes, cart-native code in ROM, the EasyFlash banking discipline from…
6502-debugging
Use when a C64 program misbehaves at runtime — crashes, corruption, wrong values, dead input, visual glitches — and you need a procedure, not a guess. Symptom-indexed playbook of runtime debugging procedures using c64-tools.
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…