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/thewaywithin/agent-11/meta-devnpx skills add TheWayWithin/agent-11 --skill meta-devgit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/meta-dev)<a href="https://agentmods.dev/skills/thewaywithin/agent-11/meta-dev"><img src="https://agentmods.dev/badge/skills/thewaywithin/agent-11/meta-dev.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.00107 | $0.01074 |
| Opus 5 | $0.00053 | $0.00537 |
| Sonnet 5 | $0.00021 | $0.00215 |
| Haiku 4.5 | $0.00011 | $0.00107 |
Grade A, and why
meta-dev 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 today.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENT-11 Meta-Development
What this skill is for
You are working inside the AGENT-11 framework repository, not a user product. Edits here ship to other people via install.sh. The same filename can mean two different things depending on directory.
This skill orients you correctly without relying on memory or repeated reminders.
Two parallel agent sets in this repo
| Path | Role | Modify when |
|---|---|---|
project/agents/specialists/ |
Library agents — deployed to users via install.sh |
You are improving agent capabilities for end users (≥99% of work) |
.claude/agents/ |
Working squad — internal dev tooling | You are improving how we build AGENT-11 itself (rare) |
Same distinction for commands:
| Path | Role | Modify when |
|---|---|---|
project/commands/ |
Library commands — deployed | Improving end-user /coord, /foundations, etc. |
.claude/commands/ |
Working squad commands — internal | Improving internal dev workflows |
Default work target
When in doubt: project/agents/specialists/ and project/commands/. Most work improves what users get on install.sh, not our internal tooling.
CLAUDE.md hierarchy in this repo
| File | Purpose | Deployed? |
|---|---|---|
/CLAUDE.md |
Jamie's personal preferences | NO |
library/CLAUDE.md |
AGENT-11 library instructions → user's .claude/CLAUDE.md post-install |
YES |
.claude/CLAUDE.md |
Working-squad project guardrails | NO |
Edits to library content target library/CLAUDE.md. Personal preferences belong in root. Internal dev guardrails belong in .claude/CLAUDE.md.
Verification before significant edits
Before editing an agent or command file, ask:
- Am I improving the AGENT-11 library for end users? →
project/agents/specialists/orproject/commands/ - Am I improving the AGENT-11 development process? →
.claude/agents/or.claude/commands/ - Quick check:
grep -n "$(basename your-file)" project/deployment/scripts/install.sh— if found, it's deployed (library); if not, it's internal.
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.
- today First seen · 91 lines · 107 tokens per session scan A cba7662c785b
meta-dev is a skill published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 12d ago), licensed MIT. It adds 107 tokens to every session and 1,074 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-09-04.
Other skills, from other repositories
ensemble-implement-trd-beads
Implement TRD with beads project management — persistent bead hierarchy, dependency-aware execution via br/bv, and cross-session resumability (Codex skill for /ensemble:implement-trd-beads).
ensemble-beads-build
Drive an existing bead hierarchy to completion through the full builder, code-review, and close pipeline (Codex skill for /ensemble:beads-build).
skills
Version: 1.0.0 Target: .NET 8.0+ with Blazor Server/WebAssembly UI Library: Microsoft Fluent UI Blazor Components Purpose: Fast lookup for common Blazor patterns and best practices.
phoenix
Quick reference for Phoenix and Elixir development patterns. For comprehensive documentation, see REFERENCE.md.
git-town
This skill should be used when the user asks to "create a feature branch", "start a new feature", "sync my branch", "sync with main", "update from main", "create a PR", "create a pull request", "ship a feature", "merge and clean up", "handle merge conflicts", "resolve conflicts in git-town", "create stacked branches"…
flyio
Version: 1.0.0 | Target Size: <25KB | Purpose: Fast reference for Fly.io deployments and global application distribution.