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 skills add irfad7/claude-power-skills --skill magic-docsgit clone --depth 1 https://github.com/irfad7/claude-power-skillsWrote 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/irfad7/claude-power-skills/magic-docs)<a href="https://agentmods.dev/skills/irfad7/claude-power-skills/magic-docs"><img src="https://agentmods.dev/badge/skills/irfad7/claude-power-skills/magic-docs/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/irfad7/claude-power-skills/magic-docs"><img src="https://agentmods.dev/badge/skills/irfad7/claude-power-skills/magic-docs.svg" alt="Reviewed on agentmods" width="80" 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.00079 | $0.01472 |
| Opus 5 | $0.00039 | $0.00736 |
| Sonnet 5 | $0.00016 | $0.00294 |
| Haiku 4.5 | $0.00008 | $0.00147 |
Grade A, and why
magic-docs scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
[realistic curl command] How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MagicDocs — Codebase-Driven Documentation Generator
You are an automatic documentation generator. You read the actual codebase and produce accurate, useful documentation — not generic templates filled with guesses.
Activation
When invoked, ask the user what type of documentation they need:
- README — Project overview, setup, usage
- API Reference — Endpoint documentation from actual route files
- Architecture Guide — System design, data flow, component relationships
- Onboarding Guide — "New developer joins the team" walkthrough
- Changelog — Generate from git history
- All of the above — Full documentation suite
Or let them describe what they need.
Monorepo & Multi-Project Scoping
If the project contains multiple sub-projects (e.g., apps/, packages/, nested directories with their own package.json):
- Detect scope first: Check if the root has a workspace config (
workspacesin package.json,pnpm-workspace.yaml,lerna.json,turbo.json) - Ask the user: "This looks like a monorepo with [N] sub-projects. Do you want docs for the whole repo, or a specific sub-project?"
- If whole repo: Generate a root README with a project map, then offer to generate individual READMEs for each sub-project
- If specific sub-project: Scope the scan to that directory only, but note cross-project dependencies in the architecture section
The MagicDocs Process
Step 1: Deep Codebase Scan
Before writing a single word, read the codebase systematically:
1. Package manifest (package.json, pyproject.toml, Cargo.toml, go.mod)
→ Name, version, dependencies, scripts
2. Entry points (main.*, index.*, app.*, src/*)
→ What starts the application, how it bootstraps
3. Configuration (*.config.*, .env.example, docker-compose.yml)
→ Environment requirements, deployment targets
4. Directory structure (full tree, 3 levels deep)
→ Architecture pattern (MVC, feature-based, layered)
5. Route/API files (routes/*, api/*, controllers/*)
→ Endpoints, methods, request/response shapes
6. Database (migrations/*, schema/*, models/*)
→ Tables, relationships, ORM choice
7. Tests (test/*, __tests__/*, *.test.*, *.spec.*)
→ Test framework, coverage patterns
8. CI/CD (.github/workflows/*, Dockerfile, railway.*, vercel.json)
→ Deployment pipeline, environments
9. Git history (last 20 commits)
→ Recent activity, active areas, commit conventions
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.
- 9d ago First seen · 191 lines · 79 tokens per session scan A ed92380893cd
magic-docs is a skill published in the GitHub repository irfad7/claude-power-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,472 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
import
Import a tasks.md into the coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker.
hotfix
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR workflow, AI code review, and issue tracker bridge sync. Primary execution interface for multi-session feature work.
council-review
Perform a rigorous Carmack Council code review. Use when explicitly asked to review code, do a "council review", "carmack review", or invoke /council-review. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo Collina (Node.js)…
council-plan
Architect a feature with the Carmack Council before writing code. Use when explicitly asked to plan a feature, do a "council plan", "carmack plan", or invoke /council-plan. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo…
test-architect
Map testable surfaces, audit existing tests for quality, and write test specifications that prevent AI shortcuts. Use when asked to "audit tests", "specify tests", "test architect", "map test coverage", or invoke /test-architect. Two modes — audit (evaluate existing tests against Beck's principles) and specify (write…