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/matrixfounder/agentic-development/skill-reverse-engineeringnpx skills add MatrixFounder/Agentic-development --skill skill-reverse-engineeringgit clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWhat 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.00015 | $0.00718 |
| Opus 5 | $0.00008 | $0.00359 |
| Sonnet 5 | $0.00003 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
skill-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 yesterday.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reverse Engineering Skill
Purpose
Recover the mental model of a project from its codebase when documentation is outdated or missing.
When to Use
- Documentation-code mismatch detected
- New team member onboarding
- Post-"quick fix" cleanup
Strategy: Automated Scan + Iterative Analysis
Phase 1: Automated Directory Scan
Tool: scripts/scan_structure.py
Usage:
python3 .agent/skills/skill-reverse-engineering/scripts/scan_structure.py . --depth 2
Goal:
- Get high-level overview of project structure.
- Identify dominant languages and components.
- Avoid context overflow by NOT reading all files.
Phase 2: Local Analysis (Per-Directory)
For each key component identified in Phase 1:
- List files.
- Sample 2-3 representative files (read content).
- Generate Local Summary:
- Purpose
- Key Classes
- Dependencies
Phase 3: Global Synthesis
Combine local summaries to update docs/ARCHITECTURE.md:
- Update Directory Structure
- Update Component Map
- Identify Architecture Drift (Code != Docs)
Output Artifacts
1. ARCHITECTURE.md Update
Generate diffs for:
- Directory Structure
- Component Map
- Data Flow
2. KNOWN_ISSUES.md Updates
Identify:
TODO/HACKcomments indicating tech debt.- Discrepancies between implementation and docs.
Filing format (thin index). docs/KNOWN_ISSUES.md is a hand-maintained thin index, not a
flat checklist — do NOT append - [ ] lines to it. The authoritative format contract lives in the
known-issues-format skill (artifact-management, TIER 0, delegates to it) — follow it:
- If
docs/KNOWN_ISSUES.mddoes not exist yet, materialize it fromknown-issues-format'sassets/templates/known_issues_md_template.mdfirst (create-if-absent). - File each finding as its own
docs/issues/<slug>.md(frontmatter + H1 + body) plus one index line under the matching## <category>heading — edit both in lockstep. - If a finding needs a category/prefix the project's ledger doesn't have yet, add a new prefix → category row to that ledger's Rules / Conventions table before filing.
What ships with it
1 file 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.
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.
- yesterday First seen · 87 lines · 15 tokens per session scan A f7c3d3f72e2b
skill-reverse-engineering is a skill published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 15 tokens to every session and 718 once invoked, about $0.0001 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-31.
Other skills, from other repositories
add-tests
Generates tests for existing code. Analyzes the target function, method, or class to identify the happy path, error cases, and edge cases, then writes test cases following the project's testing framework and naming conventions. Invoked when the user asks to add tests, write tests, cover code, or increase coverage.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
company-hiring-intelligence
Reverse-engineer what a company is building by scraping their job postings, careers page, LinkedIn Jobs, and engineering blog using TinyFish web agents. Use whenever a user wants to understand a company's strategic direction from hiring signals, do competitive intelligence, figure out a tech stack from job…
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).