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 instructions/sergeyfedyakov/v8help-mcp/agents-mdgit clone --depth 1 https://github.com/sergeyfedyakov/v8help-mcpWrote 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/instructions/sergeyfedyakov/v8help-mcp/agents-md)<a href="https://agentmods.dev/instructions/sergeyfedyakov/v8help-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sergeyfedyakov/v8help-mcp/agents-md.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.00736 | $0.00736 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
v8help-mcp AGENTS.md 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Проектные инструкции
Индексация Kilo (семантический поиск)
В этом проекте включено индексирование Kilo (см. kilo.jsonc → indexing.enabled: true).
Перед операциями, которые зависят от семантического поиска (semantic_search) или индексации:
- Прочитай
kilo.jsoncи проверьindexing.enabledиindexing.provider. - Провайдер эмбеддинга — LM Studio (OpenAI-совместимый endpoint
http://localhost:1234/v1), модельtext-embedding-qwen3-embedding-0.6b(мультиязычная, 1024 измерения, поддерживает русский). Перед операциями индексации убедись, чтоhttp://localhost:1234/v1/modelsотвечает (GET запрос). - Если не отвечает — запусти
lms server startкак фоновый процесс (инструмент background_process). Процесс автоматически остановится при завершении сессии Kilo. После старта повторно проверь/v1/models; если нужной embedding-модели нет в списке — загрузи её черезlms load <идентификатор>и укажи в запросе. - Проверь, что сервер отдаёт эмбеддинги размерности 1024 (соответствует
indexing.dimension).
Статус "IDX Disabled" (consent в VS Code)
Симптом: конфиг и провайдер настроены верно, но индексация не стартует, статус Disabled.
Причина: в VS Code индексация дополнительно управляется consent (разрешением на проект), а не только indexing.enabled. Пока consent не установлен, статус Disabled с сообщением Codebase indexing is disabled until you enable it for this project in Kilo Settings.. UI-тумблеры в некоторых версиях расширения (например 7.4.20) consent НЕ выставляют, поэтому они не помогают.
Обходной путь — выставить consent напрямую через внутренний HTTP-API процесса kilo:
- Найди порт сервера (обычно процесс
kilo.exeиз VS Code):netstat -ano | findstr LISTENINGи сопоставь по PID. - Basic-аутентификация: логин
kilo, пароль из$env:KILO_SERVER_PASSWORD. PUT http://127.0.0.1:<порт>/indexing/consent?directory=<URL-encoded путь проекта>с телом{"enabled":true}и заголовкомx-kilo-directory: <путь проекта>.- Проверь статус:
GET http://127.0.0.1:<порт>/indexing/status?directory=<путь>— должен статьIn Progress/Complete.
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 · 33 lines · 736 tokens per session scan A b9bda95e02af
v8help-mcp AGENTS.md is an instructions file published in the GitHub repository sergeyfedyakov/v8help-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 736 tokens to every session, about $0.0037 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.