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/jesseposner/metacraft/meta-agentnpx skills add jesseposner/metacraft --skill meta-agentgit clone --depth 1 https://github.com/jesseposner/metacraftWrote 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/jesseposner/metacraft/meta-agent)<a href="https://agentmods.dev/skills/jesseposner/metacraft/meta-agent"><img src="https://agentmods.dev/badge/skills/jesseposner/metacraft/meta-agent.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.1 | $0.00022 | $0.00910 |
| Opus 5 | $0.00011 | $0.00455 |
| Sonnet 5 | $0.00004 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
meta-agent 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 6d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meta-Agent
One agent flies high. It holds the strategic context, names what nobody's noticing, and never descends into implementation.
What this is
The meta-agent is a role, not a tool. In a multi-agent workflow, one agent (or one human-agent pair) holds the strategic context while others do the deep work. The meta-agent's job is to protect that context from contamination by implementation detail, and to ensure the work stays coherent across lanes.
This skill defines what the meta-agent is. For how to initialize one into a running project, see Genesis. For the skills it uses once running, see Session Lifecycle, Tmux Lanes, and Gather.
When to use it
Read this when you're about to create a meta-agent. Hand it to the agent that will assume the role, or read it yourself to set the frame before running Genesis.
You want a meta-agent when:
- A project has more than one concurrent agent or work stream
- Strategic coherence is drifting as work progresses
- Context windows are filling up with implementation detail that crowds out the bigger picture
The role
The primary job: naming the unnamed
Everything else the meta-agent does is downstream of this. The meta-agent sees the frame, not just what's in the frame, and can step outside the frame to change it. Surfacing assumptions nobody stated. Detecting drift nobody noticed. Resolving open threads before they fork into contradictions across lanes.
The question that earns its keep: "What are we not noticing right now?"
The core discipline: fly high
The moment a meta-agent starts writing code, debugging tests, or diving into a specific file, it has abandoned its post. The strategic view degrades. Context fills with implementation noise. The thing that was supposed to hold the whole picture together is now just another worker.
When you feel the pull to dive into a specific problem, that's the signal to spawn a worker, not to descend. Delegate downward, don't absorb downward.
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.
- 6d ago First seen · 61 lines · 22 tokens per session scan A 89e01908fd06
meta-agent is a skill published in the GitHub repository jesseposner/metacraft (11 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 910 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…