Borrowing it
Nothing to install: this file belongs to ammilam/mcp-vibe-coding-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ammilam/mcp-vibe-coding-tools/main/.github/instructions/app-development.instructions.mdgit clone --depth 1 https://github.com/ammilam/mcp-vibe-coding-toolsWrote 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/ammilam/mcp-vibe-coding-tools/app-development)<a href="https://agentmods.dev/instructions/ammilam/mcp-vibe-coding-tools/app-development"><img src="https://agentmods.dev/badge/instructions/ammilam/mcp-vibe-coding-tools/app-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/ammilam/mcp-vibe-coding-tools/app-development"><img src="https://agentmods.dev/badge/instructions/ammilam/mcp-vibe-coding-tools/app-development.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00249 | $0.00249 |
| Opus 5.5 | $0.00100 | $0.00100 |
| Sonnet 5.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 2mo 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.
- 2mo 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 9mo ago), licensed MIT. It adds 249 tokens to every session, about $0.0010 per session on Opus 5.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.
mcp-vibe-coding-tools app-development.instructions.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| mcp-vibe-coding-tools app-development.instructions.mdammilam/mcp-vibe-coding-tools | Instructions file | 1 | 9mo ago | MIT | A | 249 | GitHub Copilot |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | today | MIT | A | 7,461 | Codex, OpenCode |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | yesterday | MIT | A | 4,680 | Codex, OpenCode |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 5,516 | GitHub Copilot |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 3,093 | GitHub Copilot |
| deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness | Instructions file | 274k | 2d ago | MIT | A | 4,313 | Codex, OpenCode |