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/r2000-analyze-blocks/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/r2000-analyze-blocks)<a href="https://agentmods.dev/skills/ricardoquesada/regenerator2000/r2000-analyze-blocks"><img src="https://agentmods.dev/badge/skills/ricardoquesada/regenerator2000/r2000-analyze-blocks/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/r2000-analyze-blocks"><img src="https://agentmods.dev/badge/skills/ricardoquesada/regenerator2000/r2000-analyze-blocks.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 Prompt Injection · line 25 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00050 | $0.03669 |
| Opus 5 | $0.00025 | $0.01835 |
| Sonnet 5 | $0.00010 | $0.00734 |
| Haiku 4.5 | $0.00005 | $0.00367 |
Grade A, and why
r2000-analyze-blocks 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 11d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Blocks Workflow
Use this skill when the user asks to "analyze blocks", "convert blocks", "identify data regions", "classify the program", or wants the AI to scan a range (or the entire binary) and mark regions with their correct block types.
Overview
When a binary is loaded in Regenerator 2000, the auto-analyzer traces reachable code starting from the entry point and marks those regions as Code. Everything else remains Undefined — these are the blocks that have not yet been explored. The goal of this skill is to walk through the undefined/unexplored regions, identify what each one actually is, and convert it to the appropriate block type. This is a fundamental step in reverse engineering — separating code from data, text from tables, and pointers from raw bytes.
Block Types Reference
Use r2000_set_data_type with the data_type enum value from the right column (except for Code, where you must use r2000_disassemble).
| Block Type | data_type value / Tool |
When to Use |
|---|---|---|
| Code | Call r2000_disassemble |
Do NOT use r2000_set_data_type! Instead, execute r2000_disassemble at the entry point address. |
| Byte | byte |
Raw 8-bit data: sprite data, bitmap data, charset data, lookup tables, variables, or unknown data. |
| Word | word |
16-bit little-endian values: 16-bit variables, math constants, SID frequency values. |
| Address | address |
16-bit little-endian pointers to memory locations. Creates cross-references. For jump tables & vectors. |
| PETSCII Text | petscii |
PETSCII-encoded strings: game messages, prompts, high score names, print routine data. |
| Screencode Text | screencode |
Screen code text: data written directly to Screen RAM ($0400–$07E7). |
| Lo/Hi Address | lo_hi_address |
Split address table: first half = low bytes, second half = high bytes. Even byte count required. |
| Hi/Lo Address | hi_lo_address |
Split address table: first half = high bytes, second half = low bytes. Even byte count required. |
| Lo/Hi Word | lo_hi_word |
Split word table: first half = low bytes, second half = high bytes. E.g., SID frequency tables. |
| Hi/Lo Word | hi_lo_word |
Split word table: first half = high bytes, second half = low bytes. |
| External File | external_file |
Large binary blobs: SID music files, raw bitmaps, character sets that should be exported as-is. |
| Undefined | undefined |
Reset a region to unknown state. Use to undo a wrong classification. |
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.
- 11d ago First seen · 244 lines · 50 tokens per session scan A 3fad6193466a
r2000-analyze-blocks is a skill published in the GitHub repository ricardoquesada/regenerator2000 (164 stars, last pushed 16d ago), licensed Apache-2.0. It adds 50 tokens to every session and 3,669 once invoked, about $0.0003 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-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…