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/pr-pm/prpm/creating-agents-mdgit clone --depth 1 https://github.com/pr-pm/prpmWhat 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.00028 | $0.01207 |
| Opus 5 | $0.00014 | $0.00603 |
| Sonnet 5 | $0.00006 | $0.00241 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
creating-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 2d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating agents.md Files
Quick reference for creating agents.md files - plain markdown project context for AI coding assistants.
Schema: https://github.com/pr-pm/prpm/blob/main/packages/converters/schemas/agents-md.schema.json
Format Rules
| Requirement | Value |
|---|---|
| Format | Plain markdown only |
| Frontmatter | None (forbidden) |
| Structure | Free-form |
| File | agents.md in project root |
Critical Requirements
- No frontmatter: Pure markdown only (no YAML)
- Single file: Typically
agents.mdin project root - Plain markdown: Standard markdown syntax
- Free-form content: No required structure
What to Include
High Priority:
- Project overview and purpose
- Architecture decisions and patterns
- Tech stack and dependencies
- File structure and organization
- Coding conventions
- Development workflow
- Testing approach
- Domain knowledge and business logic
Skip:
- General programming best practices
- Language syntax explanations
- Framework basics
- Obvious code quality rules
Example: Full Stack App
# TaskMaster Development Guide
## Project Overview
TaskMaster is a task management application for remote teams with real-time collaboration and offline-first architecture.
## Architecture
### Frontend
- React 18 with TypeScript
- Vite for build tooling
- Zustand for state management
- Tailwind CSS for styling
### Backend
- Node.js with Express
- PostgreSQL with Prisma ORM
- WebSocket for real-time features
- Redis for caching and pub/sub
## Coding Conventions
- Use TypeScript strict mode
- Functional components with hooks (no class components)
- Colocate tests with source files (*.test.tsx)
- Use Zod for runtime validation
## File Structure
\`\`\`
src/
components/ # Reusable UI components
features/ # Feature-based modules
hooks/ # Custom React hooks
lib/ # Utility functions
pages/ # Route pages
\`\`\`
## Development Workflow
1. Create feature branch from `main`
2. Write tests first (TDD)
3. Implement feature
4. Run `pnpm test` and `pnpm lint`
5. Create PR with description
## Testing
- Vitest for unit tests
- Playwright for E2E tests
- 80% coverage target
- Mock external dependencies
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.
- 2d ago First seen · 217 lines · 28 tokens per session scan A b0d0d4819b23
creating-agents-md is a cursor rule published in the GitHub repository pr-pm/prpm (120 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 1,207 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
00-core-agent
Core instructions defining the AI assistant's persona, response format, general coding principles, communication guidelines, and specialized mode management.
Accessibility-Review
Reviews web interfaces, content, or code snippets for common accessibility (a11y) issues based on WCAG guidelines, ensuring usability for people with disabilities.
Security-Audit
Reviews code, configurations, or architecture designs for common security vulnerabilities and adherence to security best practices, referencing standards like OWASP Top 10.
ShadcnUI
Best practices and guidelines for working with shadcn/ui components across various frameworks.
Supabase
Guidelines for using Supabase Auth, Database (Postgres migrations), Storage, Realtime, Edge Functions, and AI/Vectors.
API-Docs
Generates or refines API reference documentation, detailing endpoints, parameters, request/response formats, authentication methods, and error codes. Focuses on technical accuracy and developer usability.