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 skills/sseshachala/conductai/booster-contextnpx skills add sseshachala/conductai --skill booster-contextgit clone --depth 1 https://github.com/sseshachala/conductaiWrote 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/sseshachala/conductai/booster-context)<a href="https://agentmods.dev/skills/sseshachala/conductai/booster-context"><img src="https://agentmods.dev/badge/skills/sseshachala/conductai/booster-context.svg" alt="Measured on agentmods" 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.00050 | $0.00394 |
| Opus 5 | $0.00025 | $0.00197 |
| Sonnet 5 | $0.00010 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
booster-context 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- booster-context — 100% identical, 0 lines differ
What it actually says
When to use
Prefer Agent Booster tools over native Read/Grep whenever the project has been indexed:
mcp__agent-booster__search_context— semantic search across all symbols (replaces Grep)mcp__agent-booster__smart_read— returns only the relevant slice of a file for a task (replaces Read)mcp__agent-booster__get_symbols— survey a file's structure before readingmcp__agent-booster__route_model— pick the right model tier (haiku/sonnet/opus) based on task complexity
Setup
pip install 'agent-booster[full]' # includes embeddings + file watcher
booster init claude # wire MCP, hooks, CLAUDE.md
booster start # background daemon — model warm + file watcher
Daemon commands
booster start # start daemon in background
booster stop # stop daemon
booster status # show pid, uptime, watcher state
With the daemon running:
search_contextresponds in ~50ms instead of 2-3s (no model cold-start)- File changes are automatically re-indexed within 2s (no manual
booster index)
Indexing
booster index # incremental — only re-indexes changed files
booster index --force # full re-index of everything
booster embed # rebuild embeddings after manual index
Gains
Run booster gain to see token savings statistics for the current session.
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.
- 5d ago First seen · 46 lines · 50 tokens per session scan A 5261b590ed7a
booster-context is a skill published in the GitHub repository sseshachala/conductai (30 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 394 once invoked, about $0.0003 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 skills, from other repositories
background-task
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.
agent-tool
Add a new tool/function the AI agent can call (e.g. look something up, hit an external API, perform an action). Use when extending the assistant's capabilities, wiring a new function into the agent, or when the model needs a new action. This project uses {{ cookiecutter.aiframework }}.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
rag-knowledge
Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.
channel-bot
Work with messaging-channel bots (Telegram / Slack) — register a bot, route inbound messages through the AI agent, handle webhooks vs polling, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery.