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/kilo-org/kilocode/session-historygit clone --depth 1 https://github.com/Kilo-Org/kilocodeWrote 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/agents/kilo-org/kilocode/session-history)<a href="https://agentmods.dev/agents/kilo-org/kilocode/session-history"><img src="https://agentmods.dev/badge/agents/kilo-org/kilocode/session-history.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 | $0.00013 | $0.02603 |
| Opus 5 | $0.00006 | $0.01301 |
| Sonnet 5 | $0.00003 | $0.00521 |
| Haiku 4.5 | $0.00001 | $0.00260 |
Grade A, and why
session-history scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -u "kilo:$KILO_SERVER_PASSWORD" \ How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session history and search
Kilo Code keeps local session metadata and chat history so you can resume earlier work. You can search session titles in the history UI or CLI, ask the agent to search chat content, or inspect the local SQLite database directly.
{% callout type="info" %}
Local sessions use SQLite, not PostgreSQL. Use kilo db or sqlite3, not psql, to inspect the local database.
{% /callout %}
Choose a search method
Different search surfaces cover different content and scopes:
| Method | Searches | Scope |
|---|---|---|
| VS Code History | Session titles | Sessions loaded in the selected Local, Cloud, or Worktree history view |
| JetBrains History | Session titles | Sessions loaded in the selected Local or Cloud history view |
| CLI Past chats | Session titles | Current workspace |
kilo session list --search |
Session titles | Current workspace, or every local workspace with --all |
| Ask Kilo to recall past chats | Titles and high-signal chat content | Current workspace and related Git worktrees |
| VS Code chat search | Rendered content in the open session | Current chat session |
| VS Code Past chats | Session titles and worktree names | Current workspace and related Git worktrees, including Agent Manager worktrees |
| SQLite query | Any stored field you select | Entire selected local database |
History and CLI list searches do not search message content. To find a string inside prompts or replies, ask Kilo to search past chats or use a direct SQLite query.
Search in the UI
{% tabs %} {% tab label="VS Code" %}
Search session history in VS Code
- Open the Kilo Code sidebar.
- Select the History button in the sidebar title bar. You can also select Show History below the recent sessions on a new chat.
- Select Local or Cloud.
- Enter part of a session title in Search sessions.
- Select a result to reopen it.
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.
- 3d ago First seen · 291 lines · 13 tokens per session scan A 60be6f1cf989
session-history is an agent published in the GitHub repository Kilo-Org/kilocode (27,119 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 2,603 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Create-Issue
Analyzes uncommitted changes, commit, or commit range, and creates GitHub issues and CHANGELOG entries.
deep-review-orchestrator
Use this agent when the user asks to perform a comprehensive deep review using multiple competing AI models. Trigger phrases include: 'perform a deep review with multiple perspectives' 'get competing reviews of these changes' 'conduct a thorough review using different models' 'review these changes with multiple LLMs'…
inspector-driver
Drives the vscode-inspector MCP against a live VS Code + GitLens instance and returns raw evidence (probe values, console/log excerpts, geometry, measurements) as text. Default executor for live-inspection driving so the Opus orchestrator only reasons over distilled results. Returns evidence; does NOT judge, fix, or…
backseat-dev
Backseat Driver VS Code extension development — ClojureScript shadow-cljs, Ex action/effect framework, MCP socket server, Calva REPL integration, structural editing tools, Datascript output log, skill authoring, REPL-driven interactive programming. Use when: developing Backseat Driver features, debugging extension…
bd-tester
Agent for testing Backseat Driver tools.
bootstrap
Mission: Initialize and converge a governed, structured project context for GAAI.