Borrowing it
Nothing to install: this file belongs to pooriaarab/vibedonate. 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/pooriaarab/vibedonate/main/AGENTS.mdgit clone --depth 1 https://github.com/pooriaarab/vibedonateWrote 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/pooriaarab/vibedonate/agents-md)<a href="https://agentmods.dev/instructions/pooriaarab/vibedonate/agents-md"><img src="https://agentmods.dev/badge/instructions/pooriaarab/vibedonate/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/pooriaarab/vibedonate/agents-md"><img src="https://agentmods.dev/badge/instructions/pooriaarab/vibedonate/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.00597 | $0.00597 |
| Opus 5.5 | $0.00239 | $0.00239 |
| Sonnet 5.5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
vibedonate 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 1mo 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- viberadio AGENTS.md — 91% identical, 16 lines differ
- vibedating AGENTS.md — 88% identical, 16 lines differ
- vibemovie AGENTS.md — 88% identical, 24 lines differ
- vibeshare AGENTS.md — 84% identical, 11 lines differ
- vibenetwork AGENTS.md — 83% identical, 10 lines differ
- vibelive AGENTS.md — 81% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Brand and design context
Read .agents/brand.md before changing public copy or documentation.
Read .agents/design.md before changing CLI output, prototypes, or launch media.
Pull requests
One issue. One PR. One concern. Under 500 counted lines.
Open the issue first. No issue, no branch. The issue number ties the branch, the title, the body and the merged commit to one agreed piece of work.
branch: vdo-<issue>-<slug> vdo-142-fix-onboarding-drop-off
title: [VDO-<issue>] <Subject> [VDO-142] Fix onboarding drop-off
body: Closes #142
## What / ## Why / ## How I verified
Assisted-by: <agent>:<model>
Subject line: imperative mood, 10-50 characters, no trailing period, no emoji. Write "Fix the drop-off", not "Fixed the drop-off".
Hard caps, failed by the pr-standards CI check: 500 counted lines, 40 counted
files, exactly one Closes #. Lockfiles, build output, snapshots, generated
code and migrations are not counted. There is no label that clears the cap and
no one to ask for one. Split the change.
Settings for this repo are in .github/pr-standards.json. The standard is at
https://github.com/pooriaarab/scripts/blob/main/pr-standards.md
Cloud agents (Cursor)
This repo runs on Cursor Cloud Agents. Local
.env.local does not sync — mirror keys in Dashboard → Cloud Agents → Secrets.
| Secret type | Use for |
|---|---|
| Runtime Secret | API keys, passwords (hidden from chat/commits) |
| Environment Variable | Non-sensitive config (URLs, flags) |
| Build Secret | Private npm/docker registries during install only |
Install & test
Install command lives in .cursor/environment.json. After dashboard setup:
- Environments → link this repo → wait for Build = Success
- Secrets → copy every key from your local
.env.local/.env.example - Run the project's test/lint command before opening a PR (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.
- 1mo ago First seen · 74 lines · 597 tokens per session scan A ec778cd963f2
vibedonate AGENTS.md is an instructions file published in the GitHub repository pooriaarab/vibedonate (0 stars, last pushed yesterday), licensed MIT. It adds 597 tokens to every session, about $0.0024 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-09-04.
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.