Borrowing it
Nothing to install: this file belongs to maddexritter-rgb/vibe-editing. 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/maddexritter-rgb/vibe-editing/main/AGENTS.mdgit clone --depth 1 https://github.com/maddexritter-rgb/vibe-editingWrote 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/maddexritter-rgb/vibe-editing/agents-md)<a href="https://agentmods.dev/instructions/maddexritter-rgb/vibe-editing/agents-md"><img src="https://agentmods.dev/badge/instructions/maddexritter-rgb/vibe-editing/agents-md/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/maddexritter-rgb/vibe-editing/agents-md"><img src="https://agentmods.dev/badge/instructions/maddexritter-rgb/vibe-editing/agents-md.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.00328 | $0.00328 |
| Opus 5.5 | $0.00131 | $0.00131 |
| Sonnet 5.5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
vibe-editing AGENTS.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 today.
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
Vibe Editing — agent entrypoint
For the first setup or production request (make/edit/deliver clips), read ONBOARDING.md and run
python3 plugins/vibe-editing/onboard.py status before starting production. Resume missing setup
one question at a time. Keys and access follow the current /edit stack documented in
docs/CONNECTIONS.md: AssemblyAI primary transcription, Gemini listener, and selected audit/fallback
connections. The active agent reads the bundled editorial documents and makes the cut/style
decisions. Never ask for an Anthropic/OpenAI key or a separate Claude CLI. Team live-brain access
is provisioned once rather than asking each editor to create a token. Do not invent substitute providers.
This interview is not required for read-only questions or work on the repository's code/docs.
Do the setup work for the user. Secrets go into private hidden prompts or private local files,
never chat, command arguments, tracked files, screenshots or logs. The deliberately bundled
read-only editorial-brain token in config/editorial-brain.json is the sole shared-access exception;
use it automatically and never substitute a database-admin or personal provider credential. Mark configured, verified,
pending and skipped precisely. Missing team bridges/playbooks are pending dependencies; an
accepted API key is not proof the native editing pipeline is installed.
Then read CLAUDE.md for workflow routing. Use only this kit, the deliberately bundled team reader, and the user's own provider credentials.
Making clips does not authorize external uploads, social publishing, or Topaz processing.
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.
- today First seen · 21 lines · 328 tokens per session scan A f9d287a59225
vibe-editing AGENTS.md is an instructions file published in the GitHub repository maddexritter-rgb/vibe-editing (28 stars, last pushed yesterday), licensed MIT. It adds 328 tokens to every session, about $0.0013 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-10-27.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.