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/crain99/cocos-reverse-engineering-skill/cocos-reverse-engineeringnpx skills add Crain99/cocos-reverse-engineering-skill --skill cocos-reverse-engineeringgit clone --depth 1 https://github.com/Crain99/cocos-reverse-engineering-skillWrote 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/crain99/cocos-reverse-engineering-skill/cocos-reverse-engineering)<a href="https://agentmods.dev/skills/crain99/cocos-reverse-engineering-skill/cocos-reverse-engineering"><img src="https://agentmods.dev/badge/skills/crain99/cocos-reverse-engineering-skill/cocos-reverse-engineering.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 | $0.00099 | $0.02466 |
| Opus 5 | $0.00049 | $0.01233 |
| Sonnet 5 | $0.00020 | $0.00493 |
| Haiku 4.5 | $0.00010 | $0.00247 |
Grade A, and why
cocos-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 4d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cocos Creator Reverse Engineering
Recover the editable project (scripts + scenes + assets + meta) from a compiled Cocos Creator build. Supports Cocos Creator 2.3.x / 2.4.x (the src/project.js + res/ layout and the main.js + assets/ layout) and Cocos Creator 3.x (the assets/main/ bundle layout with config.json + import/ + native/ + cocos-js/). Handles XXTEA-encrypted .jsc scripts via auto key extraction.
The workflow is driven by cc-reverse, a Node.js CLI that this skill wraps and extends with engine detection and decryption helpers.
Prerequisites
This skill requires Node.js 16+ and the cc-reverse CLI installed. Run the dependency checker to verify:
bash ${CLAUDE_PLUGIN_ROOT}/skills/cocos-reverse-engineering/scripts/check-deps.sh
If anything is missing, follow ${CLAUDE_PLUGIN_ROOT}/skills/cocos-reverse-engineering/references/setup-guide.md, or let the install helper handle it:
bash ${CLAUDE_PLUGIN_ROOT}/skills/cocos-reverse-engineering/scripts/install-dep.sh cc-reverse
Workflow
Phase 1: Verify and install dependencies
bash ${CLAUDE_PLUGIN_ROOT}/skills/cocos-reverse-engineering/scripts/check-deps.sh
The output contains machine-readable lines:
INSTALL_REQUIRED:<dep>— must be installed before proceeding (node,cc-reverse).INSTALL_OPTIONAL:<dep>— nice-to-have (7z,unzip,ffmpegfor audio format conversion).
If required dependencies are missing (exit code 1), install them:
bash ${CLAUDE_PLUGIN_ROOT}/skills/cocos-reverse-engineering/scripts/install-dep.sh <dep>
Re-run the check until everything passes. Do not proceed to Phase 2 until all required dependencies are OK.
Phase 2: Detect the project layout
Cocos Creator ships three distinct build layouts. Before anything else, identify which one you're looking at — the rest of the workflow branches on this.
Action: Run the detector script.
bash ${CLAUDE_PLUGIN_ROOT}/skills/cocos-reverse-engineering/scripts/detect-project.sh <path-to-build>
What ships with it
12 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.
- references/asset-recovery-patterns.md 6.0 KB
- references/cc-reverse-usage.md 5.4 KB
- references/cocos2x-format.md 5.7 KB
- references/cocos3x-format.md 14 KB
- references/jsc-decryption.md 4.8 KB
- references/setup-guide.md 4.1 KB
- scripts/check-deps.sh 3.4 KB runs code
- scripts/detect-project.sh 5.9 KB runs code
- scripts/find-assets.sh 3.0 KB runs code
- scripts/find-jsc-key.sh 4.2 KB runs code
- scripts/install-dep.sh 6.1 KB runs code
- scripts/unpack-cocos.sh 4.0 KB runs code
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.
- 4d ago First seen · 161 lines · 99 tokens per session scan A 5f2fb411089c
cocos-reverse-engineering is a skill published in the GitHub repository Crain99/cocos-reverse-engineering-skill (37 stars, last pushed 4mo ago), licensed MIT. It adds 99 tokens to every session and 2,466 once invoked, about $0.0005 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
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
build-game-monster-system
Build, integrate, audit, or refactor rigged monsters for Three.js and web action games. Use for monster asset contracts, procedural or imported creature rigs, semantic joints and sockets, hurtboxes and attack volumes, combat animation states, enemy-runtime adapters, LODs, deterministic review fixtures, and validating…
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…