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/dalehurley/codewithphp/vitepress-usagegit clone --depth 1 https://github.com/dalehurley/codewithphpWhat 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.00021 | $0.02344 |
| Opus 5 | $0.00010 | $0.01172 |
| Sonnet 5 | $0.00004 | $0.00469 |
| Haiku 4.5 | $0.00002 | $0.00234 |
Grade A, and why
vitepress-usage 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.
How it starts
The opening of the file, as written. The whole thing — 488 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VitePress Usage for Code with PHP
Development Commands
# Start local development server
npm run dev
# Site available at http://localhost:5173
# Build static site for production
npm run build
# Output: docs/.vitepress/dist
# Preview production build locally
npm run preview
# Useful for testing before deployment
Project Structure
docs/
├── .vitepress/
│ ├── config.ts # Site configuration
│ └── theme/ # Custom theme (if any)
├── index.md # Homepage
├── public/
│ └── CNAME # Custom domain configuration
└── series/
└── <series-slug>/
├── index.md # Series overview
├── chapters/ # All chapter markdown files
│ ├── 00-chapter.md
│ ├── 01-chapter.md
│ └── ...
└── code/ # Code examples colocated with content
├── 00-topic/
├── 01-topic/
└── ...
Adding a New Series
Step 1: Create Series Directory Structure
# Create the series directories
mkdir -p docs/series/<series-slug>/{chapters,code}
# Create the series index
touch docs/series/<series-slug>/index.md
Step 2: Create Series Index
The series index must include:
- Comprehensive overview (4-6 paragraphs)
- Who This Is For section
- Prerequisites (software, time, skills)
- What You'll Build (deliverables)
- Learning Objectives
- How This Series Works (methodology)
- Learning Path Overview (visual diagram)
- Quick Start (5-minute example)
- Chapters (organized by parts with descriptions)
- FAQ
- Getting Help
- Related Resources
See docs/series/php-basics/index.md as the reference template.
Step 3: Update VitePress Config
Edit docs/.vitepress/config.ts:
// Add to nav
nav: [
// ... existing items
{
text: 'Series Name',
link: '/series/series-slug/'
}
],
// Add sidebar configuration
sidebar: {
// ... existing sidebars
'/series/series-slug/': [
{
text: 'Series Name',
items: [
{
text: 'Overview',
link: '/series/series-slug/'
},
{
text: 'Part 1: Section Name',
collapsed: false,
items: [
{
text: '00 — Chapter Title',
link: '/series/series-slug/chapters/00-chapter-slug'
},
{
text: '01 — Chapter Title',
link: '/series/series-slug/chapters/01-chapter-slug'
}
]
}
]
}
]
}
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 · 488 lines · 21 tokens per session scan A a88a2e0bb6d4
vitepress-usage is a cursor rule published in the GitHub repository dalehurley/codewithphp (5 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 2,344 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-31.
Other cursor rules, from other repositories
cursorrules
Cursor rule "cursorrules" from The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge, covering agentic coding: humans design, agents code!, agentic coding steps, example llm project file structure, pocket flow and core abstraction.
rapid-domain-mastery
Use the rapid-domain-mastery workflow for source-heavy learning, literature onboarding, qualifying exam prep, and deep diagnostic tutoring.
claude-code-skills
辅助用户掌握 Skills 能力的学习与开发指南.
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.