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 jessymariau/booboo --skill booboo-orggit clone --depth 1 https://github.com/jessymariau/boobooWrote 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/jessymariau/booboo/booboo-org)<a href="https://agentmods.dev/skills/jessymariau/booboo/booboo-org"><img src="https://agentmods.dev/badge/skills/jessymariau/booboo/booboo-org/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/jessymariau/booboo/booboo-org"><img src="https://agentmods.dev/badge/skills/jessymariau/booboo/booboo-org.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.00095 | $0.01175 |
| Opus 5 | $0.00048 | $0.00588 |
| Sonnet 5 | $0.00019 | $0.00235 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
booboo-org 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 11d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The organigram — run a fleet like a company
Read RULES.md first. Rules 6 and 7 are the load-bearing ones here.
org.booboo.json is SOURCE, not output. It is versioned, validated before
every write (a cycle can never land), and edited through the panel or a reviewed
change. The chart is not a diagram of the authority — it is the authority.
Agents that boot with booboo_boot obey the shape on their next session.
First: is this brain shaped at all?
If org.booboo.json contains "seed": true, it still holds the scaffold's sample
Writer/Researcher pair, which belongs to nobody.
Stop and run the project's ONBOARDING.md before any other work. Do not add
agents, do not write memories against the sample agents, do not build on the
placeholder. Everything downstream inherits from the org, so work done against a
fake structure gets redone against the real one.
Read before you ask
Most of an organigram is already in the project. Look, in this order:
package.json/pyproject.toml/go.mod— what this is and what it is built from- the README and any architecture doc — what it claims to do, for whom, and how the parts relate
- the top two directory levels — candidate divisions
- an existing
CLAUDE.md/AGENTS.md/.cursorrules— conventions already agreed git log --oneline -40andgit shortlog -sn— what actually gets worked on, by how many peopledocs/,ops/,infra/— surfaces that need an owner
Then ask the human only what the repo could not tell you.
Folders give you nouns, not shape
This is the mistake to design against. A directory listing is flat by construction. An org built straight from one is a root with fifteen children and no structure — which is a list, not an organigram, and it makes rule inheritance useless because there is nowhere to declare a rule except the root.
The grouping almost always lives in the prose. "X is the contract at the centre, Y and Z feed it, A and B render it" is three divisions, and no amount of staring at folder names will produce it. Read for how the parts relate, then group the nouns underneath.
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.
- 11d ago First seen · 103 lines · 95 tokens per session scan A 2d7ddc81f14d
booboo-org is a skill published in the GitHub repository jessymariau/booboo (1 stars, last pushed 28d ago), licensed MIT. It adds 95 tokens to every session and 1,175 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-08-31.
Other skills, from other repositories
potpie-source-ingestion
Use when the user explicitly asks to ingest, refresh, or deeply understand a repository, PR, issue, ticket, runbook, incident report, document, or web link into Potpie. The harness performs todo-driven discovery, uses local/GitHub/integration tools and read-only subagents when available, builds evidence-backed…
potpie-repo-baseline
Use when establishing, refreshing, or deeply understanding a repository's baseline memory in Potpie: purpose, application type, features, services/modules, environments, deploy shape, dependencies, API contracts, datastores, integrations, ownership, and explicit preferences. The harness reads authored and…
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
potpie-change-timeline
Use when an agent needs recent or historical change context: what changed recently, regressions, merged PRs, tickets, docs, incidents, deployments, releases, and source-history ingestion.
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.