Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jessymariau/booboonpx agentmods add skills/jessymariau/booboo/booboo-adapterWrote 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-adapter)<a href="https://agentmods.dev/skills/jessymariau/booboo/booboo-adapter"><img src="https://agentmods.dev/badge/skills/jessymariau/booboo/booboo-adapter/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-adapter"><img src="https://agentmods.dev/badge/skills/jessymariau/booboo/booboo-adapter.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.00071 | $0.00969 |
| Opus 5.5 | $0.00028 | $0.00388 |
| Sonnet 5.5 | $0.00014 | $0.00194 |
| Haiku 4.5 | $0.00007 | $0.00097 |
Grade A, and why
booboo-adapter 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 2mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapters — a small file, never a fork
Read RULES.md first. Rule 3 is the whole skill in one line: ship the shortest
adapter, never a fork.
Why this stays cheap
Booboo is a small JSON spec at the centre with adapters feeding it and consumers rendering it. Emit conformant JSON and you inherit the 3D viewer, the REST API, the MCP server, the panel and the vault for free — none of them know or care where the nodes came from.
That is deliberate. The spec is roughly a kilobyte of contract precisely so that
supporting a weird source costs a small file rather than a maintained fork. Read
SPEC.md before writing anything; if the job appears to need a fork, you have
almost certainly misread it.
Try the escape hatch first
The json adapter is passthrough and it is the universal answer:
sources:
- adapter: json
path: ./data/extra.booboo.json
For a one-off import, an export script that writes conformant JSON plus this adapter beats a custom adapter, because there is nothing left to maintain. Reach for a real adapter when the source needs to be re-read on every build.
What an adapter owes the spec
Whatever the source, the output is nodes and links:
- nodes — a stable
id, a humanlabel, alayer, optionallyparent(the spine),cluster,weight,icon, and adatapayload - links —
source,target,type
Two things decide whether the graph is readable rather than a hairball:
Stable ids. An id that changes between builds turns one node into two and
silently orphans every authored [[link]] pointing at the old one. Derive ids
from something the source guarantees — a primary key, a slug — never from a
mutable label or an array index.
Parent, deliberately. parent builds the spine that makes the 3D view legible
and the hierarchy meaningful. Everything defaulting to the root produces a flat
starburst that renders fine and tells you nothing. If the source has no natural
parent, group in the adapter and say so in a comment.
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.
- 2mo ago First seen · 93 lines · 71 tokens per session scan A 25153f542bf6
booboo-adapter is a skill published in the GitHub repository jessymariau/booboo (1 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 969 once invoked, about $0.0003 per session on Opus 5.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
rails
Use when creating or modifying Ruby files under src/backend/ in a Ruby on Rails service — controllers, ActiveRecord models, routes.rb, concerns, migrations, the rescuefrom error chain, and their RSpec specs. Triggers on any .rb change under src/backend/. Covers thin controllers + strong parameters, model-owned…
sf-knowledge-sfFieldRef
Apply Salesforce knowledge and best practices for Salesforce Field Reference Guide.
sf-knowledge-soql-sosl
Apply Salesforce knowledge and best practices for SOQL and SOSL Reference.
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.