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/marcinhamiga/code-indexing-mcp/feature-devnpx skills add MarcinHamiga/code-indexing-mcp --skill feature-devgit clone --depth 1 https://github.com/MarcinHamiga/code-indexing-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.00033 | $0.01198 |
| Opus 5 | $0.00016 | $0.00599 |
| Sonnet 5 | $0.00007 | $0.00240 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
feature-dev 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running a structured feature-development workflow. Follow the phases in order. Do not skip or merge phases.
The feature request is $request. If it is missing or too vague to plan against (no clear goal or acceptance signal), ask the user with the AskUserQuestion tool before starting Phase 1.
Phase 1 — Gather current state with code-indexing-mcp
The core rule of this phase: the code-indexing-mcp tools are the primary navigation mechanism. Do not fall back to Grep/Glob/Read for code exploration while they are available.
- Call
mcp__code-indexing-mcp__project_statusfor the target project. If the project is unknown, callmcp__code-indexing-mcp__list_projectsand, if needed,mcp__code-indexing-mcp__init_project. - If the index is missing or stale relative to the files the feature will touch, call
mcp__code-indexing-mcp__index_projectfirst. Tell the user if indexing will take a moment. - Explore the relevant parts of the codebase:
mcp__code-indexing-mcp__search_code— issue several targeted semantic queries derived from the feature request (the area being changed, the patterns it must follow, the tests that cover it). Not one broad query.mcp__code-indexing-mcp__file_outline— get a file's structure before reading it; decide which parts matter instead of dumping whole files.mcp__code-indexing-mcp__find_symbol— locate the declarations the feature will touch. It matches declaration names only; usefind_referencesfor call sites.- When changing an existing declaration,
mcp__code-indexing-mcp__find_references— identify structural uses from its selectedchunk_idor project/path/qualified-symbol tuple. For a rename or signature change, usemcp__code-indexing-mcp__analyze_refactorand retain itslikely_change,review, and limitation findings in the plan. For an approved rename, produce the mechanical edits withmcp__code-indexing-mcp__emit_refactor_patchafter reviewing the analysis — it emits a reviewable unified diff (git apply-able) for the deterministic subset only, never edits source, and reports the rest inunapplied/conflicted. Both analysis tools cover only C#, Go, Java, JavaScript, Python, Rust, TSX, and TypeScript declarations — selecting one in any other language returnsUNSUPPORTED_LANGUAGE, not an empty result, so fall back tosearch_code/grep for that part of the codebase instead of treating silence as "no usages". Checkcompleteness.state(complete,complete_with_dynamic_limitations, orincomplete) and thelimitationslist before trusting a finding set as exhaustive. mcp__code-indexing-mcp__get_chunk— pull the full body of a chunk when you need exact code.
- Only use Grep when the task genuinely needs a literal match semantic search cannot express (exact string literals, config keys, TODO/FIXME markers) or when the MCP tools are unavailable — and say so when you do.
End the phase with a short current-state summary for the user: the modules/files involved, existing patterns and conventions the feature must follow, extension points, and how that area is tested.
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 · 62 lines · 33 tokens per session scan A 9c23fc3e3c6e
feature-dev is a skill published in the GitHub repository MarcinHamiga/code-indexing-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 1,198 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.