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 agentmods add skills/ricardoquesada/regenerator2000/r2000-analyze-programnpx skills add ricardoquesada/regenerator2000 --skill r2000-analyze-programgit 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/r2000-analyze-program)<a href="https://agentmods.dev/skills/ricardoquesada/regenerator2000/r2000-analyze-program"><img src="https://agentmods.dev/badge/skills/ricardoquesada/regenerator2000/r2000-analyze-program.svg" alt="Measured on agentmods" 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.00032 | $0.03700 |
| Opus 5 | $0.00016 | $0.01850 |
| Sonnet 5 | $0.00006 | $0.00740 |
| Haiku 4.5 | $0.00003 | $0.00370 |
Grade A, and why
r2000-analyze-program 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 6d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Program Workflow
Use this skill when the user asks to "analyze this program", "analyze everything", "full analysis", or wants a complete end-to-end pass over the loaded binary — classifying blocks, documenting routines, and naming symbols.
This skill orchestrates the following existing skills in order:
r2000-analyze-blocks— Classify all memory regions (code vs data vs text, etc.).r2000-analyze-routine— Analyze and document each subroutine.r2000-analyze-symbol— Analyze and name each data symbol.
Phase 0 — Gather Context & Entropy Unpack Check
Before starting or launching any subagents, you must gather context and check if the binary is packed/compressed.
- Get Binary Info: Call
r2000_get_binary_info.- Read the returned
"entropy"value. - Also read the description of the
r2000_get_binary_infotool (e.g. fromtools/list) to find the entropy threshold preference (e.g.,7.5). - If the binary's
entropyis greater than or equal to the threshold (values above the threshold suggest the binary might be compressed):- Ask the user (using regular text in chat) if they would like to unpack the binary before proceeding with the analysis.
- If the user accepts:
- Call the
r2000_unpack_binarytool. - Note:
r2000_unpack_binaryis a destructive action (clears existing comments/labels/blocks) and may take up to 10 seconds or more. - If
r2000_unpack_binaryreturns an error: The binary was not unpacked. Log the failure and continue the analysis on the current binary. - If it succeeds: The binary has been unpacked and a new unpacked binary has been loaded in its place. You must restart this phase (Phase 0) from scratch, calling
r2000_get_binary_infoagain to fetch the new unpacked binary's info and continue.
- Call the
- If the user declines: Continue the analysis on the current binary.
- Read the returned
Phase 1 — Classify Blocks (r2000-analyze-blocks)
Block classification is a prerequisite for all subsequent analysis.
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.
- 6d ago First seen · 234 lines · 32 tokens per session scan A 2d1c91bcc612
r2000-analyze-program is a skill published in the GitHub repository ricardoquesada/regenerator2000 (164 stars, last pushed 11d ago), licensed Apache-2.0. It adds 32 tokens to every session and 3,700 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…