reverse-document

reverse-document is a skill for Claude Code from HolyMonkey/youtube-example-ai-studio. It costs 24 tokens per session (2,022 once invoked), scanned A, a copy of reverse-document, MIT.

A documentation workflow that creates design or architecture documents from existing game code or prototypes.

In plain words
What is it for?
Use it to document game mechanics, software architecture decisions, or prototype concepts from a file or directory.
Why use it?
It records how an implemented system works when the original planning documents are missing or outdated.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to document game mechanics, software architecture decisions, or prototype concepts from a file or directory.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/holymonkey/youtube-example-ai-studio/reverse-document
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 HolyMonkey/youtube-example-ai-studio --skill reverse-document
Clone the repo
git clone --depth 1 https://github.com/HolyMonkey/youtube-example-ai-studio

Made for: Claude Code.

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-document

README.md
[![agentmods](https://agentmods.dev/badge/skills/holymonkey/youtube-example-ai-studio/reverse-document.svg)](https://agentmods.dev/skills/holymonkey/youtube-example-ai-studio/reverse-document)
Your own site
<a href="https://agentmods.dev/skills/holymonkey/youtube-example-ai-studio/reverse-document"><img src="https://agentmods.dev/badge/skills/holymonkey/youtube-example-ai-studio/reverse-document.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,022 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 100% copy Near-identical to another mod 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.00024 $0.02022
Opus 5 $0.00012 $0.01011
Sonnet 5 $0.00005 $0.00404
Haiku 4.5 $0.00002 $0.00202

Measured 3d ago against content hash 133839df766a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

reverse-document 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 3d 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.

Origin

This is a copy

100% identical to reverse-document — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/reverse-document/SKILL.md · 263 lines

How it starts

The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reverse Documentation

This skill analyzes existing implementation (code, prototypes, systems) and generates appropriate design or architecture documentation. Use this when:

  • You built a feature without writing a design doc first
  • You inherited a codebase without documentation
  • You prototyped a mechanic and need to formalize it
  • You need to document "why" behind existing code

Workflow

1. Parse Arguments

Format: /reverse-document <type> <path>

Type options:

  • design → Generate a game design document (GDD section)
  • architecture → Generate an Architecture Decision Record (ADR)
  • concept → Generate a concept document from prototype

Path: Directory or file to analyze

  • src/gameplay/combat/ → All combat-related code
  • src/core/event-system.cpp → Specific file
  • prototypes/stealth-mech/ → Prototype directory

Examples:

/reverse-document design src/gameplay/magic-system
/reverse-document architecture src/core/entity-component
/reverse-document concept prototypes/vehicle-combat

2. Analyze Implementation

Read and understand the code/prototype:

For design docs (GDD):

  • Identify mechanics, rules, formulas
  • Extract gameplay values (damage, cooldowns, ranges)
  • Find state machines, ability systems, progression
  • Detect edge cases handled in code
  • Map dependencies (what systems interact?)

For architecture docs (ADR):

  • Identify patterns (ECS, singleton, observer, etc.)
  • Understand technical decisions (threading, serialization, etc.)
  • Map dependencies and coupling
  • Assess performance characteristics
  • Find constraints and trade-offs

For concept docs (prototype analysis):

  • Identify core mechanic
  • Extract emergent gameplay patterns
  • Note what worked vs what didn't
  • Find technical feasibility insights
  • Document player fantasy / feel

3. Ask Clarifying Questions (Collaborative Protocol)

DO NOT just describe the code. ASK about intent:

Design questions:

  • "I see a stamina system that depletes during combat. Was this for:
    • Pacing (prevent spam)?
    • Resource management (strategic depth)?
    • Or something else?"
  • "The stagger mechanic seems central. Is this a core pillar, or supporting feature?"
  • "Damage scales exponentially with level. Intentional power fantasy, or needs rebalancing?"

Read the full file on GitHub · 263 lines

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. 3d ago First seen · 263 lines · 24 tokens per session scan A 133839df766a

Subscribe to this mod's changes

reverse-document is a skill published in the GitHub repository HolyMonkey/youtube-example-ai-studio (11 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 2,022 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to reverse-document, differing in 0 lines, and is treated as a copy.