mcp-vibe-coding-tools autonomous-development.instructions.md

mcp-vibe-coding-tools autonomous-development.instructions.md is an instructions file for GitHub Copilot from ammilam/mcp-vibe-coding-tools. It costs 2,671 tokens per session, scanned A, original, MIT.

Instructions for letting an AI agent carry out software development tasks from planning through validation without routine human approval. They define a workflow for understanding requirements, writing code, testing, and checking the result.

In plain words
What is it for?
For handling coding tasks end to end, including planning, implementation, error handling, logging, tests, documentation, and automatic checks.
Why use it?
They reduce the need to supervise each development step and make validation part of the normal workflow.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/ammilam/mcp-vibe-coding-tools/autonomous-development
Clone the repo
git clone --depth 1 https://github.com/ammilam/mcp-vibe-coding-tools

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for mcp-vibe-coding-tools autonomous-development.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ammilam/mcp-vibe-coding-tools/autonomous-development.svg)](https://agentmods.dev/instructions/ammilam/mcp-vibe-coding-tools/autonomous-development)
Your own site
<a href="https://agentmods.dev/instructions/ammilam/mcp-vibe-coding-tools/autonomous-development"><img src="https://agentmods.dev/badge/instructions/ammilam/mcp-vibe-coding-tools/autonomous-development.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,671 This file is loaded in full into every session.
When invoked 2,671 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02671 $0.02671
Opus 5 $0.01336 $0.01336
Sonnet 5 $0.00534 $0.00534
Haiku 4.5 $0.00267 $0.00267

Measured 3d ago against content hash daf4283f4851, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-vibe-coding-tools autonomous-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 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.

.github/instructions/autonomous-development.instructions.md · 418 lines

How it starts

The opening of the file, as written. The whole thing — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Autonomous Development Instructions

Core Principle: Zero Human Intervention

You are empowered to operate fully autonomously. Complete all development tasks end-to-end without requiring human approval or intervention unless explicitly blocked by missing credentials, hardware access, or external service failures.

Autonomous Development Workflow

1. Understanding & Planning (Auto-Execute)

  • Analyze requirements thoroughly before writing any code
  • Break down complex tasks into discrete, testable units
  • Create implementation plan with clear success criteria
  • Document assumptions and architectural decisions upfront
  • NO APPROVAL NEEDED - proceed directly to implementation

2. Implementation (Fully Autonomous)

  • Write production-ready code on first attempt
  • Include comprehensive error handling for all edge cases
  • Add logging and observability from the start
  • Follow language/framework best practices automatically
  • Use MCP tools to validate code as you write it
  • Create tests alongside code - never defer testing
  • Generate documentation inline and in separate docs

3. Validation (Auto-Execute All Checks)

Execute ALL validation steps automatically without asking:

Code Quality:

  • Run linters (npm run lint, eslint, pylint, etc.)
  • Check code formatting (prettier, black, etc.)
  • Verify type safety (tsc --noEmit, mypy, etc.)
  • FIX ALL ISSUES IMMEDIATELY - do not report and wait

Testing:

  • Run unit tests (npm test, pytest, etc.)
  • Run integration tests if they exist
  • Check code coverage - aim for >80%
  • FIX FAILING TESTS IMMEDIATELY - iterate until green

Build Verification:

  • Compile/build the project (npm run build, cargo build, etc.)
  • Verify no build errors or warnings
  • FIX BUILD ISSUES IMMEDIATELY - do not stop until it builds

Security & Performance:

  • Run security scanners if available (npm audit, safety check, etc.)
  • Check for common vulnerabilities
  • Profile performance-critical code paths
  • FIX CRITICAL ISSUES - document minor ones

Read the full file on GitHub · 418 lines

Changes

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.

  1. 3d ago First seen · 418 lines · 2,671 tokens per session scan A daf4283f4851

Subscribe to this mod's changes

mcp-vibe-coding-tools autonomous-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 2,671 tokens to every session, about $0.0134 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.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens