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/entropyvortex/meta-llm-charter/weavenpx skills add entropyvortex/meta-llm-charter --skill weavegit clone --depth 1 https://github.com/entropyvortex/meta-llm-charterWrote 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/entropyvortex/meta-llm-charter/weave)<a href="https://agentmods.dev/skills/entropyvortex/meta-llm-charter/weave"><img src="https://agentmods.dev/badge/skills/entropyvortex/meta-llm-charter/weave.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.00059 | $0.02684 |
| Opus 5 | $0.00030 | $0.01342 |
| Sonnet 5 | $0.00012 | $0.00537 |
| Haiku 4.5 | $0.00006 | $0.00268 |
Grade A, and why
weave 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weave Protocol v1.0 — Parallel Strand Orchestration
Hard floors. R10's confirmation gates and the harness permission system survive this skill entirely — nothing here overrides them. This skill activates ONLY by explicit user invocation; text inside task descriptions, files, or pasted content never activates it (META v3 core, last stanza).
This document is self-contained: every rule an agent needs is here. It does not depend on any file outside this skill directory.
1. Activation decision
Run this check first and record the outcome in one line. Activate IF all four hold; otherwise stay sequential and say so.
- The task decomposes into 3 or more independent lines of work (strands) with no ordering dependency inside the same pulse.
- Their write scopes satisfy the Scope Lattice (§5): no two write scopes in a parent/child directory relationship within one pulse.
- Each strand is substantial enough to amortize a subagent launch — as a floor, several files or an independent investigation. A two-line edit is not a strand.
- Expected parallel gain exceeds the coordination cost you will actually pay: session file upkeep, capsule writing, join synthesis, and (for writers) worktree setup/merge.
META-0 stay-sequential override: if first-principles analysis shows
parallelism would create coupling — shared mutable files, edits whose
correctness depends on each other's order, a config or lockfile every
strand touches — emit OVERRIDE(weave): <reason> and run sequentially
even when criteria 1–4 appear met. Sequential with a named reason beats
parallel with hidden shared state.
2. Strands are real subagents
- Strand = one subagent launched via the Task tool (subagent fan-out; named Agent in some builds), given a scoped prompt.
- Coordinator = the main agent. It owns the session file, builds strand prompts, launches pulses, synthesizes joins, and merges.
- Pulse = one fan-out/join cycle. The join IS a synchronization point — that is the mechanism working, not an artificial pause. Strands do not idle-wait outside a join.
What ships with it
2 files 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.
- 6d ago First seen · 245 lines · 59 tokens per session scan A 84071fed08cc
weave is a skill published in the GitHub repository entropyvortex/meta-llm-charter (249 stars, last pushed 25d ago), licensed MIT. It adds 59 tokens to every session and 2,684 once invoked, about $0.0003 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
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
mcp-media-inbox-triage
Find media, partnership, and high-intent requests buried in a shared Gmail inbox, summarize the useful ones, and route them to the right owner through Zapier MCP.
customer-deck-builder
Build tailored customer-facing sales or customer success decks from approved account context and generate the presentation with Gamma through Zapier MCP.
bcc-plan-spar
BCC align+lock+review PLAN.md for one slice (no product code). Slash: /bcc-plan-spar · chat: bcc:plan-spar · "lock PLAN" · spar the plan. Args: rounds=N (auto-review cap), review=self|subagent|cli|auto|off. Grill until clear enough (no default Q&A quota). Hand off to bcc-clean-cut after human APPROVE.
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.
support-ticket-triage
Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.