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/elara-labs/code-context-engine/tabninegit clone --depth 1 https://github.com/elara-labs/code-context-engineWhat 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.00011 | $0.00374 |
| Opus 5 | $0.00005 | $0.00187 |
| Sonnet 5 | $0.00002 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
tabnine 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 yesterday.
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
Tabnine uses a project-local settings file and an instruction file for MCP integration.
Quick setup
cce init # Auto-detects Tabnine if .tabnine/ exists
cce init --agent all # Explicitly includes Tabnine
Files created
.tabnine/agent/settings.json
Registers the CCE MCP server for Tabnine's agent.
{
"mcpServers": {
"context-engine": {
"command": "cce",
"args": ["serve", "--project-dir", "/path/to/your/project"]
}
}
}
TABNINE.md
Contains instructions for Tabnine to prefer context_search for code retrieval. The CCE block is wrapped in markers so your own content is preserved during upgrades.
Verify it's working
- Restart Tabnine after running
cce init - Use Tabnine's chat to ask a code question
- Check for
context_searchtool calls in the output - Run
cce savingsto verify queries are tracked
Troubleshooting
Tabnine doesn't detect the MCP server
Check .tabnine/agent/settings.json exists and contains the context-engine entry. If missing, re-run cce init --agent all.
"cce: command not found"
Ensure cce is on your PATH. Add ~/.local/bin to your shell profile if installed with uv tool install.
Auto-detection doesn't find Tabnine
CCE looks for a .tabnine/ directory in the project root. If it doesn't exist, use cce init --agent all to force configuration.
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.
- yesterday First seen · 56 lines · 11 tokens per session scan A 575141ecd5b8
tabnine is an agent published in the GitHub repository elara-labs/code-context-engine (407 stars, last pushed 8d ago), licensed MIT. It adds 11 tokens to every session and 374 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
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
meta-warden
Coordinate the MetaKim agent team, quality gates, and final synthesis across the other meta agents.
nopua-mentor-ja
Agent Team メンター役 — 他のチームメイトの実行状況を観察し、恐怖ではなく知恵で導く。行き詰まり、放棄、受け身に陥ったときは道徳経の知恵で啓発。5人以上のチーム推奨。.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.