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 vieko/bonfire --skill bonfiregit clone --depth 1 https://github.com/vieko/bonfireWrote 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/vieko/bonfire/bonfire)<a href="https://agentmods.dev/skills/vieko/bonfire/bonfire"><img src="https://agentmods.dev/badge/skills/vieko/bonfire/bonfire/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/vieko/bonfire/bonfire"><img src="https://agentmods.dev/badge/skills/vieko/bonfire/bonfire.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.00055 | $0.00558 |
| Opus 5.5 | $0.00022 | $0.00223 |
| Sonnet 5.5 | $0.00011 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
bonfire 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 1mo 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.
What it actually says
Bonfire (fallback skill)
Session context persistence for AI coding.
Bonfire ships in three layers:
- File convention —
<git-root>/.bonfire/index.mdwith two managed fence blocks. - Native host adapters (preferred) — drop-in plugins that auto-update the file as you work. Available for Pi and Claude Code.
- This skill (fallback) — manual
/skill:bonfire endfor agents without a native adapter (Codex, OpenCode, etc.).
If you're on Pi or Claude Code, install the adapter from ~/dev/bonfire/{pi,claude}/ instead. The adapters are zero-ritual and richer than what this skill can do.
Git root: !git rev-parse --show-toplevel 2>/dev/null || echo ""
Opt-in
The skill (and the adapters) honor an opt-in gate per repo:
mkdir <repo>/.bonfire
Without .bonfire/ present, this skill exits silently. That keeps it from polluting random repos.
Routing
| Input | Action |
|---|---|
end |
Read commands/end.md and execute |
migrate |
Read commands/migrate.md and execute. One-off migration for a pre-v7 index.md that lacks the v1 fence markers — wraps the file in fences without destroying hand-curated content. |
Earlier versions of bonfire had start and handoff commands. Both are removed in 7.0:
start: redundant. Modern agents auto-read files fromcwd, so.bonfire/index.mdis already in context. No ritual needed.handoff: Pi has a richer first-partyhandoffextension. For non-Pi agents, use Linear, a notes file consumed via@fileinjection, or a draft PR description.
What ships with it
3 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.
- 1mo ago First seen · 47 lines · 55 tokens per session scan A 96ccabdfab0d
bonfire is a skill published in the GitHub repository vieko/bonfire (10 stars, last pushed 13d ago), licensed MIT. It adds 55 tokens to every session and 558 once invoked, about $0.0002 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…