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/the-pocket/pocketflow-tutorial-codebase-knowledge/cursorrulesgit clone --depth 1 https://github.com/The-Pocket/PocketFlow-Tutorial-Codebase-KnowledgeWhat 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.13624 |
| Opus 5 | $0.00000 | $0.06812 |
| Sonnet 5 | $0.00000 | $0.02725 |
| Haiku 4.5 | $0.00000 | $0.01362 |
Grade A, and why
cursorrules 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cursorrules — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,664 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Coding: Humans Design, Agents code!
If you are an AI agents involved in building LLM Systems, read this guide VERY, VERY carefully! This is the most important chapter in the entire document. Throughout development, you should always (1) start with a small and simple solution, (2) design at a high level (
docs/design.md) before implementation, and (3) frequently ask humans for feedback and clarification. {: .warning }
Agentic Coding Steps
Agentic Coding should be a collaboration between Human System Design and Agent Implementation:
| Steps | Human | AI | Comment |
|---|---|---|---|
| 1. Requirements | ★★★ High | ★☆☆ Low | Humans understand the requirements and context. |
| 2. Flow | ★★☆ Medium | ★★☆ Medium | Humans specify the high-level design, and the AI fills in the details. |
| 3. Utilities | ★★☆ Medium | ★★☆ Medium | Humans provide available external APIs and integrations, and the AI helps with implementation. |
| 4. Node | ★☆☆ Low | ★★★ High | The AI helps design the node types and data handling based on the flow. |
| 5. Implementation | ★☆☆ Low | ★★★ High | The AI implements the flow based on the design. |
| 6. Optimization | ★★☆ Medium | ★★☆ Medium | Humans evaluate the results, and the AI helps optimize. |
| 7. Reliability | ★☆☆ Low | ★★★ High | The AI writes test cases and addresses corner cases. |
- Requirements: Clarify the requirements for your project, and evaluate whether an AI system is a good fit.
- Understand AI systems' strengths and limitations:
- Good for: Routine tasks requiring common sense (filling forms, replying to emails)
- Good for: Creative tasks with well-defined inputs (building slides, writing SQL)
- Not good for: Ambiguous problems requiring complex decision-making (business strategy, startup planning)
- Keep It User-Centric: Explain the "problem" from the user's perspective rather than just listing features.
- Balance complexity vs. impact: Aim to deliver the highest value features with minimal complexity early.
- Understand AI systems' strengths and limitations:
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 · 1,664 lines · 0 tokens per session scan A f2b18dceffa3
cursorrules is a cursor rule published in the GitHub repository The-Pocket/PocketFlow-Tutorial-Codebase-Knowledge (12,632 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 13,624 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-30.
Other cursor rules, from other repositories
ai-ml-series
AI/ML for PHP Developers series — Guidelines for writing AI and machine learning content.
claude-php-developers
Claude for PHP Developers series — Guidelines for writing Claude API integration content with PHP.
chapter-checkbox-integration
Chapter Checkbox Integration - Adding progress tracking to tutorial chapters.
authoring-guidelines
Comprehensive tutorial authoring guidelines based on php-basics series patterns.
chapter-seo-requirements
SEO requirements for tutorial chapters — meta tags, structured data, and social sharing optimization.
linking-and-sources
Internal/external linking, GitHub edit links, and licensing notes.