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/tutorials-task-templategit 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.00011 | $0.02853 |
| Opus 5 | $0.00005 | $0.01426 |
| Sonnet 5 | $0.00002 | $0.00571 |
| Haiku 4.5 | $0.00001 | $0.00285 |
Grade A, and why
tutorials-task-template 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 — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Template — Creating New Tutorials
Use this template when creating new tutorial chapters for Code with PHP. This template works in conjunction with the Global Rules — Tutorials and Authoring Guidelines.
Pre-Writing Checklist
Before you start writing, gather:
- Chapter number and position in series
- Previous chapter(s) to link in prerequisites
- Concepts being taught
- What the reader will build
- Code examples planned (list files)
- Time estimate for completion
- Difficulty level (Beginner/Intermediate/Advanced)
Metadata Template
---
title: "[NN]: [Chapter Title]"
description: "[One-sentence description of what reader will learn]"
series: "[series-slug]"
chapter: [N]
order: [N]
difficulty: "[Beginner|Intermediate|Advanced]"
prerequisites:
- "[/series/series-slug/chapters/previous-chapter]"
- "[Additional requirements if needed]"
---
Example:
---
title: "08: Introduction to Object-Oriented Programming"
description: "Learn how to model real-world concepts into reusable blueprints (classes) and create individual instances (objects)"
series: "php-basics"
chapter: 8
order: 8
difficulty: "Intermediate"
prerequisites:
- "/series/php-basics/chapters/07-mastering-string-manipulation"
---
Chapter Structure Template
Copy this template and fill in each section:
---
[frontmatter here]
---
# Chapter [NN]: [Chapter Title]
## Overview
[Write 2-4 compelling paragraphs that:]
- [Explain what this chapter covers and why it matters]
- [Connect to previous learning: "Until now, we've..."]
- [Introduce the paradigm/concept shift if applicable]
- [Preview what they'll build by the end]
[Example: "Until now, we've been writing code in a **procedural** way: a series of steps and functions that operate on data. This is great for simple scripts, but as applications grow, it can become disorganized..."]
## Prerequisites
Before starting this chapter, you should have:
- PHP 8.4+ installed and confirmed working with `php --version`
- Completion of [Chapter [N-1]](/series/[slug]/chapters/[prev-chapter]) or equivalent understanding
- [Specific tool or software needed]
- [Knowledge/skill requirement]
- **Estimated Time**: ~[XX] minutes
[Optional verification section:]
**Verify your setup:**
```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 · 495 lines · 11 tokens per session scan A 967703388f83
tutorials-task-template is a cursor rule published in the GitHub repository dalehurley/codewithphp (5 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 2,853 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.