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 guhcostan/claude-mega-brain --skill migrategit clone --depth 1 https://github.com/guhcostan/claude-mega-brainWrote 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/guhcostan/claude-mega-brain/migrate)<a href="https://agentmods.dev/skills/guhcostan/claude-mega-brain/migrate"><img src="https://agentmods.dev/badge/skills/guhcostan/claude-mega-brain/migrate.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00147 | $0.00969 |
| Opus 5 | $0.00073 | $0.00485 |
| Sonnet 5 | $0.00029 | $0.00194 |
| Haiku 4.5 | $0.00015 | $0.00097 |
Grade A, and why
migrate 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 8d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
migrate — Migrate Existing Docs to OKF
Reads existing project documentation and generates OKF concept files so claude-mega-brain can inject them at session start. The goal is exact fidelity — preserve real column names, actual formulas, and specific values, not generic descriptions.
Before starting
Look for existing OKF files: any .md with type: frontmatter, or index.md / log.md anywhere in the project. If none exist, run /mega-brain:init first.
If .mega-brain.json defines dir, place new files under that directory. Otherwise, put files wherever fits the project (docs/, project root, etc.) — no dedicated folder is required.
Process
1. Discover sources
Scan the project root. Priority order:
| Source | Look for |
|---|---|
| API specs | openapi.yaml, swagger.json, *.openapi.yml |
| DB schemas | schema.sql, schema.prisma, *.dbml, migration files |
| Data models | models/, entities/, domain/ |
| README sections | ## API, ## Schema, ## Architecture, ## Data |
| Runbooks | docs/runbook*, runbooks/, playbooks/ |
| Env/config docs | .env.example with comments, annotated config/ files |
| Existing wikis | docs/, wiki/, pages/ |
Report what you found before proceeding. If more than 10 sources, ask the user to confirm before generating all files.
2. Classify each source → OKF type
| Source content | OKF type |
|---|---|
| DB table / Prisma model | Table or BigQuery Table |
| REST/GraphQL endpoint | API |
| Business metric / KPI | Metric |
| Microservice / module | Service |
| Operational procedure | Runbook |
| Business term / glossary | Concept |
| Data pipeline / ETL | Pipeline |
3. Generate OKF files
One .md file per concept:
---
type: <classified type>
title: <name>
description: <one sentence, plain language>
resource: <source file path or URL>
tags: [<relevant tags>]
timestamp: <today ISO date>
---
# Schema / Definition
<exact content extracted from source — preserve all field names, types, values>
# Notes
<caveats, deprecations, gotchas found in the source>
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.
- 8d ago First seen · 101 lines · 147 tokens per session scan A 44bccafd34be
migrate is a skill published in the GitHub repository guhcostan/claude-mega-brain (125 stars, last pushed 1mo ago), licensed MIT. It adds 147 tokens to every session and 969 once invoked, about $0.0007 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
reduce
Extract structured knowledge from source material. Comprehensive extraction is the default — every insight that serves the domain gets extracted. For domain-relevant sources, skip rate must be below 10%. Zero extraction from a domain-relevant source is a BUG. Triggers on "/reduce", "/reduce [file]", "extract…
rethink
Challenge system assumptions against accumulated evidence. Triages observations and tensions, detects patterns, generates proposals. The scientific method applied to knowledge systems. Triggers on "/rethink", "review observations", "challenge assumptions", "what have I learned".
verify
Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".
graph
Interactive knowledge graph analysis. Routes natural language questions to graph scripts, interprets results in domain vocabulary, and suggests concrete actions. Triggers on "/graph", "/graph health", "/graph triangles", "find synthesis opportunities", "graph analysis".
remember
Capture friction as methodology notes. Three modes — explicit description, contextual (review recent corrections), session mining (scan transcripts for patterns). Triggers on "/remember", "/remember [description]".
seed
Add a source file to the processing queue. Checks for duplicates, creates archive folder, moves source from inbox, creates extract task, and updates queue. Triggers on "/seed", "/seed [file]", "queue this for processing".