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/chapter-seo-requirementsgit 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.00016 | $0.02746 |
| Opus 5 | $0.00008 | $0.01373 |
| Sonnet 5 | $0.00003 | $0.00549 |
| Haiku 4.5 | $0.00002 | $0.00275 |
Grade A, and why
chapter-seo-requirements 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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chapter SEO Requirements
Overview
Every tutorial chapter automatically receives comprehensive SEO optimization through VitePress transformHead hooks and structured data generation. This rule documents the required and optional frontmatter fields that enable SEO features.
Required Frontmatter Fields (SEO-Enabled)
These fields are mandatory and directly used for SEO:
---
title: "NN: Chapter Title"
description: "Single sentence describing what the reader will learn"
series: "php-basics" | "ai-ml-php-developers"
chapter: N
difficulty: "Beginner" | "Intermediate" | "Advanced"
---
SEO Usage
title: Used forog:title,twitter:title, and page<title>description: Used for meta description,og:description,twitter:descriptionseries: Determines social image path and schema.org Course relationshipchapter: Used for social image naming and chapter identificationdifficulty: Included in LearningResource schema aseducationalLevel
Optional SEO Enhancement Fields
Add these fields to enhance SEO and structured data:
---
# ... required fields above ...
# Optional SEO enhancements
keywords: ["PHP tutorial", "specific topic", "related term"]
author: "Code with PHP"
datePublished: "2024-10-28"
dateModified: "2024-10-28"
estimatedTime: "PT30M" # ISO 8601 duration format
teaches: ["Concept 1", "Concept 2", "Skill 3"]
---
Field Specifications
keywords (array)
- List of relevant search terms
- Used for meta keywords tag
- Helps AI crawlers understand content
- Recommended: 3-7 keywords
author (string)
- Author/organization name
- Default: "Code with PHP"
- Used in article:author meta tag
datePublished (ISO 8601 date)
- Original publication date
- Format:
YYYY-MM-DD - Used in structured data
dateModified (ISO 8601 date)
- Last modification date
- Falls back to VitePress
lastUpdatedif not provided - Used in article:modified_time meta tag
estimatedTime (ISO 8601 duration)
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 · 381 lines · 16 tokens per session scan A 531035af1082
chapter-seo-requirements is a cursor rule published in the GitHub repository dalehurley/codewithphp (5 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 2,746 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.