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-querygit 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-query)<a href="https://agentmods.dev/skills/jessymariau/booboo/booboo-query"><img src="https://agentmods.dev/badge/skills/jessymariau/booboo/booboo-query/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-query"><img src="https://agentmods.dev/badge/skills/jessymariau/booboo/booboo-query.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.00074 | $0.01006 |
| Opus 5 | $0.00037 | $0.00503 |
| Sonnet 5 | $0.00015 | $0.00201 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
booboo-query 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query a brain
Read RULES.md first — rules 5 and 6 govern every write you make here.
Boot first. Every session.
booboo_boot('<agent-id>')
Returns identity, authority chain, inherited rules, bucket reach, skills and children. Call it before deciding anything, not after — the rules it returns are binding on the work you are about to do, and reading them afterwards is how an agent discovers it just violated one.
Needs the server started with --org. If booboo_boot is missing from the tool
list, the org file was not passed.
The read path
Search before you fetch. booboo_node needs an exact id, and ids are rarely
what a human said. booboo_search ranks exact > prefix > substring; take the id
from the result and fetch with it.
booboo_search("payment webhook") → pick the id from the ranked hits
booboo_node("<that exact id>") → all fields + data
Neighbors versus path. They answer different questions:
booboo_neighbors(id, depth)— what is around this? Use to understand a thing's context, find what feeds it, spot orphans. Depth 1 first; depth 3 on a dense graph returns more than you can reason about.booboo_path(a, b)— how do these two connect? Returns the shortest chain, or null if unreachable. Use to answer "does X actually depend on Y" — and treat a null as a real answer, not a failed call.
Counts before payloads. booboo_stats gives node and link counts by layer;
booboo_count gives counts without pulling the data. Reach for these when sizing
a query — pulling a whole layer to count it is how a session runs out of context.
booboo_org returns the full organigram when you need the whole fleet rather
than one agent's slice.
The REST surface
Same graph, when MCP is not available:
/graph /stats /search /nodes/:id /neighbors/:id /path/:a/:b
Default port 8787. booboo serve --snapshot my.booboo.json --port 8787.
Writing back
Two write tools, both live — they append to the journal beside the snapshot, are queryable the same session, and survive every rebuild. No rebuild needed.
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 · 96 lines · 74 tokens per session scan A 97a6d0c5cccf
booboo-query is a skill published in the GitHub repository jessymariau/booboo (1 stars, last pushed 27d ago), licensed MIT. It adds 74 tokens to every session and 1,006 once invoked, about $0.0004 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.