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/authoring-guidelinesgit 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.00000 | $0.02445 |
| Opus 5 | $0.00000 | $0.01222 |
| Sonnet 5 | $0.00000 | $0.00489 |
| Haiku 4.5 | $0.00000 | $0.00245 |
Grade A, and why
authoring-guidelines 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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring Guidelines for Code with PHP Tutorials
This document defines the structure, formatting, and conventions for all tutorial chapters based on the established patterns in the php-basics series.
Frontmatter Requirements
Every chapter MUST include this frontmatter structure:
---
title: "NN: Chapter Title Here"
description: "One-sentence description of what the reader will learn"
series: "series-slug"
chapter: N
order: N
difficulty: "Beginner|Intermediate|Advanced"
prerequisites:
- "/series/series-slug/chapters/previous-chapter"
- "Another prerequisite if needed"
---
Field Specifications:
title: Format as "NN: Title" where NN is zero-padded chapter numberdescription: Single sentence, action-oriented, no period at endseries: Must match the series directory namechapterandorder: Usually the same number (but order can differ for special chapters)difficulty: One of three values: Beginner, Intermediate, Advancedprerequisites: Array of chapter links (absolute paths) or text requirements
File Naming Conventions
Chapters:
- Format:
series/<series-slug>/chapters/<nn>-<chapter-slug>.md - Use zero-padded two-digit numbers:
00,01,02, etc. - Use kebab-case for slugs:
building-a-simple-blog - Examples:
01-your-first-php-script.md,19-project-building-a-simple-blog.md
Code Samples:
- Store in
/code/<series-slug>/<chapter-nn>-topic/at the project root - Use descriptive filenames:
basic-functions.php,validation-example.php - Include a
README.mdin each code directory explaining the examples - Place exercise solutions in
/code/<series-slug>/<chapter-nn>-topic/solutions/
Chapter Structure Template
Every chapter MUST follow this exact structure:
# Chapter NN: Chapter Title
## Overview
A compelling 2-4 paragraph introduction that:
- Explains what the chapter covers and why it matters
- Connects to previous learning
- Previews what the reader will build
- Sets clear expectations
## Prerequisites
Before starting this chapter, you should have:
- Specific requirement with link
- PHP version requirement
- Software/tools needed
- **Estimated Time**: ~XX minutes
## What You'll Build
By the end of this chapter, you will have created:
- Specific deliverable 1
- Specific deliverable 2
- Knowledge/skill gained
- Working example with X features
## Quick Start (Optional)
A 5-minute copy-paste example showing the end result:
```bash
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 · 442 lines · 0 tokens per session scan A 499d02f6b8a1
authoring-guidelines is a cursor rule published in the GitHub repository dalehurley/codewithphp (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,445 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-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.