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/context-mentionsgit clone --depth 1 https://github.com/Kilo-Org/kilocodeWhat 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.00010 | $0.01989 |
| Opus 5 | $0.00005 | $0.00994 |
| Sonnet 5 | $0.00002 | $0.00398 |
| Haiku 4.5 | $0.00001 | $0.00199 |
Grade A, and why
context-mentions 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 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.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Mentions
Providing the right context helps Kilo Code understand your project and perform tasks accurately. All platforms support @-mentions for referencing files, and the agent can also discover context on its own using built-in tools like read, grep, and glob.
{% tabs %} {% tab label="VSCode" %}
The extension supports @-mention autocomplete for file paths and also uses a tool-based context model where the agent can automatically discover and read files using built-in tools.
How Context Works
When you describe a task, the agent uses its tools — read, grep, glob, and others — to find and read relevant files on its own. You don't need to explicitly point it at files in most cases; just describe what you want done and the agent will locate the right code.
@-Mention Autocomplete
Type @ in the chat input to get autocomplete suggestions. You can mention:
| Mention | Description | Example |
|---|---|---|
| File | Attach a file's contents to your message | @src/utils.ts |
| Terminal | In the sidebar, include the active VS Code terminal output. In Agent Manager, include the focused terminal for the selected session or worktree, including embedded Run and Setup tabs. | @terminal |
| Git Changes | Attach uncommitted working-tree diffs and new files | @git-changes |
| Past chats | Add a previous session's chat history as context | @ → Past chats → pick a session |
Selecting a suggestion inserts the mention and highlights it in the input. File contents, terminal output, and git changes are attached as context when you send the message.
Terminal context is limited to 500 lines or 50,000 characters. Longer output is truncated. If no terminal content is available, Kilo reports that terminal content is unavailable instead of attaching an empty file.
Referencing Past Chats
Choosing Past chats from the @ menu opens a searchable picker of sessions in the current workspace and related Git worktrees, including Agent Manager worktrees, ordered by recency. Search matches session titles and worktree names. Selecting a session inserts a highlighted mention token; when you send the message, that session's current chat history is added as context so the agent can build on the earlier conversation. Clicking the mention token opens the referenced 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.
- 3d ago First seen · 132 lines · 10 tokens per session scan A f30e20aa5626
context-mentions is an agent published in the GitHub repository Kilo-Org/kilocode (27,119 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 1,989 once invoked, about $0.0001 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
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.