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 commands/consiliency/code-index-mcp/add-featuregit clone --depth 1 https://github.com/Consiliency/Code-Index-MCPWhat 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.00000 | $0.01928 |
| Opus 5 | $0.00000 | $0.00964 |
| Sonnet 5 | $0.00000 | $0.00386 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
add-feature 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
add-feature
Add a new feature to Code-Index-MCP following the plugin-based architecture.
Feature: $ARGUMENTS[0] (Type: $ARGUMENTS[1])
1. Planning Phase
- Define feature scope and requirements
- Determine if it's a new plugin, core feature, or utility
- Identify dependencies (Tree-sitter grammars, external libraries)
- Plan integration with existing components
2. Architecture Design
For New Language Plugin:
mcp_server/
├── plugins/
│ └── $ARGUMENTS[0]_plugin/
│ ├── __init__.py
│ ├── plugin.py # Implements IPlugin interface
│ ├── AGENTS.md # AI agent configuration
│ └── CLAUDE.md # Points to AGENTS.md for instructions
For Core Feature:
mcp_server/
├── $ARGUMENTS[0].py # Core implementation
├── utils/
│ └── $ARGUMENTS[0]_helper.py # Supporting utilities
└── tests/
└── test_$ARGUMENTS[0].py # Unit tests
3. Plugin Implementation Template
# mcp_server/plugins/$ARGUMENTS[0]_plugin/plugin.py
from pathlib import Path
from typing import Iterable
from ...plugin_base import (
IPlugin, IndexShard, SymbolDef,
Reference, SearchResult, SearchOpts
)
from ...utils.treesitter_wrapper import TreeSitterWrapper
class Plugin(IPlugin):
lang = "$ARGUMENTS[0]"
def __init__(self) -> None:
self._ts = TreeSitterWrapper()
# Initialize language-specific components
def supports(self, path: str | Path) -> bool:
"""Check if file extension matches plugin."""
return Path(path).suffix in {".ext", ".extension"}
def indexFile(self, path: str | Path, content: str) -> IndexShard:
"""Parse and index file content."""
# Implementation using tree-sitter
pass
def getDefinition(self, symbol: str) -> SymbolDef | None:
"""Find symbol definition."""
pass
def findReferences(self, symbol: str) -> Iterable[Reference]:
"""Find all references to symbol."""
pass
def search(self, query: str, opts: SearchOpts | None = None) -> Iterable[SearchResult]:
"""Search for code patterns."""
pass
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 · 270 lines · 0 tokens per session scan A b0fd87c75af3
add-feature is a command published in the GitHub repository Consiliency/Code-Index-MCP (57 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,928 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.