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/pooriaarab/vibenetwork/agents-mdgit clone --depth 1 https://github.com/pooriaarab/vibenetworkWrote 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/vibenetwork/agents-md)<a href="https://agentmods.dev/instructions/pooriaarab/vibenetwork/agents-md"><img src="https://agentmods.dev/badge/instructions/pooriaarab/vibenetwork/agents-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.1 | $0.00576 | $0.00576 |
| Opus 5 | $0.00288 | $0.00288 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
vibenetwork 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 yesterday.
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.
This is a copy
83% identical to vibedonate AGENTS.md — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Read .agents/brand.md and .agents/design.md before public copy or interface work.
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: vn-<issue>-<slug> vn-142-fix-onboarding-drop-off
title: [VN-<issue>] <Subject> [VN-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)
Verify before PR
npm test
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.
- yesterday First seen · 70 lines · 576 tokens per session scan A c65a24857aa2
vibenetwork AGENTS.md is an instructions file published in the GitHub repository pooriaarab/vibenetwork (0 stars, last pushed 2d ago), licensed MIT. It adds 576 tokens to every session, about $0.0029 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to vibedonate AGENTS.md, differing in 10 lines, and is treated as a copy.
Other instructions, from other repositories
daisyui code_generation_with_git.instructions.md
Instructions for saadeghi/daisyui, covering activation, initial setup, development loop, error handling and session end.
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.
dario CLAUDE.md
Claude Code instructions for askalf/dario, covering dario — notes for claude code (and other llm coding agents), commits and prs, style, scope and codex drift runner.
granite.build AGENTS.md
AGENTS.md instructions for ibm-granite/granite.build, covering agents.md, git commits, github prs and issues, project overview and common commands.
ai-git-commiter CLAUDE.md
Instructions for zdt1013/ai-git-commiter, covering ai git commiter, 项目结构, 技术栈, 常用命令 and 安装依赖.