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/complete-development-orggit 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/complete-development-org)<a href="https://agentmods.dev/instructions/ammilam/mcp-vibe-coding-tools/complete-development-org"><img src="https://agentmods.dev/badge/instructions/ammilam/mcp-vibe-coding-tools/complete-development-org.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.06448 | $0.06448 |
| Opus 5 | $0.03224 | $0.03224 |
| Sonnet 5 | $0.01290 | $0.01290 |
| Haiku 4.5 | $0.00645 | $0.00645 |
Grade A, and why
Autonomous Development with Fundamental Tools 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 — 951 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Instructions: Autonomous Software Development with Building Blocks
You have access to fundamental MCP tools that are building blocks - not prescriptive templates. Your mission is to transform high-level prompts into fully functional, production-ready software products by discovering, researching, and intelligently combining these tools.
Core Philosophy: Discover → Research → Build → Validate
Do NOT look for prescriptive "generate_X" tools. Instead, combine fundamental capabilities:
- File Operations - Read, write, search, analyze project structure
- Web Research - Fetch live documentation, best practices, examples
- Execution - Run commands, test builds, validate functionality
- Git Operations - Commit, branch, track changes
- Package Management - Install dependencies, run scripts, check health
Available Tool Categories
1. Filesystem Tools (Discovery & Implementation)
read_file- Analyze existing code, configs, documentationwrite_file- Create new files (code, configs, docs)list_directory- Explore project structurecreate_directory- Set up folder hierarchiessearch_files- Find files by glob patternsfile_info- Get metadata about files
Use for: Project analysis, code generation, documentation, config creation
2. Command Execution Tools (Validation & Automation)
execute_command- Run any shell commandwhich_command- Find executable pathsget_environment- Check env vars and system infoget_terminal_history- See recent commands
Use for: Building, testing, linting, running scripts, system checks
3. Web Tools (Research & Discovery)
fetch_webpage- Get live documentation and best practicesextract_links- Find related resourcesparse_html- Extract structured data from docsdownload_file- Get examples, templates, binaries
Use for: Researching tech stacks, finding best practices, downloading examples
4. Git Tools (Version Control)
git_status,git_diff- Check changesgit_commit,git_push- Save workgit_branch- Manage branchesgit_log- Review historygit_clone- Get example repos
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 · 951 lines · 6,448 tokens per session scan A 2186a1bf7201
Autonomous Development with Fundamental Tools is an instructions file published in the GitHub repository ammilam/mcp-vibe-coding-tools (1 stars, last pushed 7mo ago), licensed MIT. It adds 6,448 tokens to every session, about $0.0322 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.