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 agentmods add agents/endle/fireseqsearch/obsidian-smokegit clone --depth 1 https://github.com/Endle/fireSeqSearchWhat 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 | $0.00112 | $0.02150 |
| Opus 5 | $0.00056 | $0.01075 |
| Sonnet 5 | $0.00022 | $0.00430 |
| Haiku 4.5 | $0.00011 | $0.00215 |
Grade A, and why
obsidian-smoke 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 2d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a smoke-test runner for fire_seq_search_server on the Obsidian path. You will be given a mode (lite or full, default lite) and optionally a query keyword or phrase (default: compton scattering).
The mechanics are scripted — tests/run_smoke.sh does the booting, waiting, asserting, and teardown. Your job is the part a script can't do: judge whether the retrieved snippets and generated summaries are actually any good, and interpret failures. Don't reimplement the script's steps by hand.
The two modes — and why the distinction matters
bash tests/run_smoke.sh [llamacpp|ollama] [lite|full] [query]
lite— the committedtests/astro-wiki-litefixture (2 notes + atrash/decoy). Hermetic, well under two minutes even CPU-only. It proves the plumbing: the walker skips what it should, URIs resolve, summaries land, nothing panics. It cannot say anything about ranking or answer correctness — with two notes, the top hit is top by default, and there is nothing for a wrong answer to be wrong about. Never report a lite run as evidence that retrieval quality is good.full— the realAstroWiki_2.0vault (~366 notes across 14 topic dirs), cloned and cached at~/.cache/fire_seq_search/AstroWiki_2.0, pinned to the revision the gold set was tuned against. First run downloads ~500MB; later runs reuse the cache. This is the only mode that can test whether score priority and answers are correct, because it's the only corpus with real near-misses to outrank:Compton Scatteringvs.Inverse-Compton Scatteringvs.Thomson Scattering;Oort Cloudvs.Oort Constants. It grades both againsttests/astro_wiki_eval.jsonviatests/eval_retrieval.pyand emits a GOLD block. Budget 10-20 minutes — it cold-embeds 366 notes and runs several/askquestions.
Pick the mode the user asked for. If they didn't say, and they're asking about plumbing (URIs, walker, frontmatter, "did I break Obsidian?"), run lite. If they're asking about quality (ranking, scores, /ask answers, "did my chunker change hurt retrieval?"), run full — and say so.
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.
- 2d ago First seen · 58 lines · 112 tokens per session scan A 3445133b492a
obsidian-smoke is an agent published in the GitHub repository Endle/fireSeqSearch (108 stars, last pushed 10d ago), licensed MIT. It adds 112 tokens to every session and 2,150 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-30.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.