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/ammilam/mcp-vibe-coding-tools/app-developmentgit clone --depth 1 https://github.com/ammilam/mcp-vibe-coding-toolsWhat 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.00249 | $0.00249 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
mcp-vibe-coding-tools app-development.instructions.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 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.
What it actually says
- For any application written, ensure that you create tests, documentation, and follow best practices for code structure and readability.
- Always use the tools available to you to ensure the application you are writing works as intended. This can include built-in tools or MCP tools for configured MCP servers
- When writing code, ensure that you handle errors gracefully and provide meaningful error messages to users or developers.
- Create documentation for what you write, depending on the scope of it and how many documents created, you can add them to a /docs directory or in one combined README file.
- Ensure that the app workds, that there are no linting errors, and that all tests pass before considering the application complete. If there are any issues during testing or linting, address them using your tools if possible without user intervention.
- Use the MCP tools to validate the application as needed, including any static analysis, security checks, or performance profiling tools available. This should be done without user intervention where possible.
- Follow best practices for the specific programming language and framework you are using, including naming conventions, file organization, and design patterns.
- dont add emojis or any other non-standard characters to the code or documentation.
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 · 12 lines · 249 tokens per session scan A 869aef1f7c5a
mcp-vibe-coding-tools app-development.instructions.md is an instructions file published in the GitHub repository ammilam/mcp-vibe-coding-tools (1 stars, last pushed 7mo ago), licensed MIT. It adds 249 tokens to every session, about $0.0012 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.