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 rules/vibeeval/vibecosystem/agent-developmentgit clone --depth 1 https://github.com/vibeeval/vibecosystemWhat 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.00000 | $0.00293 |
| Opus 5 | $0.00000 | $0.00147 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
agent-development 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.
What it actually says
Agent Development Rules
Agent File Format
Each agent is a Markdown file with YAML frontmatter:
---
name: agent-name
description: One-line description of what the agent does
tools: [Read, Write, Edit, Bash, Grep, Glob]
---
Followed by the agent's system prompt in Markdown.
Naming Conventions
- Filename:
kebab-case.md(e.g.,code-reviewer.md) - Name field: same as filename without extension
- Description: starts with a verb (e.g., "Reviews code for...")
Agent Categories
- Core Dev: frontend-dev, backend-dev, kraken, spark, devops
- Review & QA: code-reviewer, security-reviewer, verifier, qa-engineer
- Domain Experts: graphql-expert, kubernetes-expert, ddd-expert
- Architecture: architect, planner, clean-arch-expert
- Testing: tdd-guide, e2e-runner, arbiter, mocksmith
- Analysis: scout, sleuth, data-analyst, profiler
Quality Rules
- Every agent must have a clear, specific purpose
- Avoid overlapping responsibilities between agents
- Keep system prompts focused and actionable
- Include specific output format expectations
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 · 41 lines · 0 tokens per session scan A bf72891afd96
agent-development is a cursor rule published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 293 tokens. 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-30.
Other cursor rules, from other repositories
chronos
Time-awareness for coding agents. Consult shell clock + file mtimes before reasoning about "when" or "how long ago". No hooks on Cursor — degraded mode only.
next
Next.js roof. Bundled docs for THIS next version. App vs Pages from the tree.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.