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/jdutton/vibe-agent-toolkit/claude-mdgit clone --depth 1 https://github.com/jdutton/vibe-agent-toolkitWrote 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/jdutton/vibe-agent-toolkit/claude-md)<a href="https://agentmods.dev/instructions/jdutton/vibe-agent-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/jdutton/vibe-agent-toolkit/claude-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.08809 | $0.08809 |
| Opus 5 | $0.04405 | $0.04405 |
| Sonnet 5 | $0.01762 | $0.01762 |
| Haiku 4.5 | $0.00881 | $0.00881 |
Grade A, and why
vibe-agent-toolkit CLAUDE.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 — 632 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Development Guidelines
This document provides guidance for AI assistants and developers working on vibe-agent-toolkit.
Project Purpose
The vibe-agent-toolkit is a modular toolkit for building, testing, and deploying portable AI agents that work across various LLMs, frameworks, and deployment targets.
See docs/architecture/README.md for detailed package architecture and evolution plan.
⚠️ CRITICAL: Pre-1.0 Development Policy
BACKWARD COMPATIBILITY IS A BUG DURING v0.1.x
While this project is in v0.1.x (pre-1.0):
- ❌ DO NOT add backward compatibility layers
- ❌ DO NOT create deprecation wrappers or shims
- ❌ DO NOT re-export types for "convenience"
- ❌ DO NOT maintain old APIs alongside new ones
- ✅ DO make breaking changes freely to improve the API
- ✅ DO remove old code completely when replacing it
- ✅ DO force consumers to update (it's pre-1.0!)
Rationale: Pre-1.0 is the time to iterate rapidly and find the right abstractions. Backward compatibility adds complexity, maintenance burden, and prevents us from fixing design mistakes. Users expect breaking changes in v0.x releases.
After v1.0: We'll follow semantic versioning strictly with proper deprecation cycles.
Project-Specific Technical Principles
🚫🚫 NO VERSIONS. The npm package version is the ONLY version this project has.
Hand-maintained version constants are PROHIBITED. No const CACHE_VERSION = 1, no
SCHEMA_VERSION, no DUMP_VERSION, no *_FACET_VERSION, no *_REVISION — nothing that is a
number a human must remember to bump in order for stored data to be judged valid.
⛔ ABSOLUTELY PROHIBITED. There is no exception and no case in which one is correct. Not temporarily, not internally, not because the alternative is harder. The npm package version is the only version this project has. If you think you have found the exception, you have not — you have found a shape that should be derived or deleted (see below).
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 · 632 lines · 8,809 tokens per session scan A 008a1f30121d
vibe-agent-toolkit CLAUDE.md is an instructions file published in the GitHub repository jdutton/vibe-agent-toolkit (2 stars, last pushed 6d ago), licensed MIT. It adds 8,809 tokens to every session, about $0.0440 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.