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 booboogit 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)<a href="https://agentmods.dev/skills/jessymariau/booboo/booboo"><img src="https://agentmods.dev/badge/skills/jessymariau/booboo/booboo/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"><img src="https://agentmods.dev/badge/skills/jessymariau/booboo/booboo.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.00121 | $0.01462 |
| Opus 5 | $0.00060 | $0.00731 |
| Sonnet 5 | $0.00024 | $0.00292 |
| Haiku 4.5 | $0.00012 | $0.00146 |
Grade A, and why
booboo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Booboo — the unified operational brain
Booboo turns a system's own data into one rooted graph — structure, knowledge, memory, agents and automations fused — then serves it as a 3D view, a REST API, an MCP server, and an agent organigram you boot from.
MIT. Eight packages under the @booboo-brain/ scope. Node ≥ 18.
What it is, in one shape
your data ──▶ ADAPTERS ──▶ GRAPH JSON ──▶ CONSUMERS
(postgres, (config- (the spec, (3D viewer · REST API ·
json, …) driven) the contract) MCP server · panel · vault)
Emit the JSON and you get the viewer, the API and the MCP server for free. Weird data means a small adapter, never a fork.
Two files carry everything. brain.json is the DERIVED snapshot (regenerate,
never hand-edit). org.booboo.json is the SOURCE organigram (versioned, validated,
edited through the panel or a reviewed change).
Positioning — say this, not that
Booboo is the org-chart layer for agent fleets. That is the uncontested claim and the reason to reach for it.
Do not pitch it as a memory store. That category has hundreds of entries and
Booboo loses the comparison on the axis nobody needed a new tool for. It has
memory (booboo_remember, buckets, the journal), but memory is a feature of the
org, not the product. The novel part is operational fusion: wiring plus knowledge
plus episodic memory plus agents plus crons in one rooted, live, bootable brain
that is simultaneously a view, an API and an MCP source.
The commands (all six, verbatim)
booboo build --config booboo.config.yaml # any postgres/json → one snapshot
booboo serve --snapshot my.booboo.json --port 8787 # REST API
booboo mcp --snapshot my.booboo.json --org org.booboo.json # MCP over stdio
booboo view --snapshot my.booboo.json # 3D viewer in the browser
booboo panel --org org.booboo.json --snapshot my.booboo.json # the organigram
booboo vault --snapshot my.booboo.json --org org.booboo.json --out vault
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 · 111 lines · 121 tokens per session scan A 51aea4d87c83
booboo is a skill published in the GitHub repository jessymariau/booboo (1 stars, last pushed 27d ago), licensed MIT. It adds 121 tokens to every session and 1,462 once invoked, about $0.0006 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-graph
Use when the task can read or write the project-memory graph through the potpie CLI: discover the contract with graph catalog, read named views with graph read, resolve entity identity with graph search-entities, create validated plans with graph propose, commit plans with graph commit --verify, inspect quality with…
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…
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.
engraphis-memory
Give the agent durable, scoped, explainable memory across sessions and repositories through the Engraphis MCP tools. Use when you learn a convention, decision, bug cause/fix, or user preference worth keeping; when prior context would help before you answer or act (to avoid re-asking or re-deriving); when asked "why is…
mistakes
List past mistakes engram has learned in this project — failures, regressions, broken assumptions. Use before starting a non-trivial change to surface relevant prior failures, or when debugging to check if this issue has been seen before.
query
Query engram's local knowledge graph for structural context — function calls, imports, type relationships, mistake history, ADRs. Use when the user asks "how does X work in this project", "what calls Y", "where is Z used", or any structural question that doesn't need file content.