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/project-structuregit 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.00243 | $0.00243 |
| Opus 5 | $0.00121 | $0.00121 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
project-structure 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.
What it actually says
Project Structure
-
docs/— VitePress content root.vitepress/config.ts— site configuration (title, base, nav, sidebar)index.md— landing page and series entry pointsseries/<series-slug>/index.md— series overview (self-contained)series/<series-slug>/chapters/<nn>-<chapter-slug>.md— numbered chaptersseries/<series-slug>/code/— chapter code samples colocated with content
-
.cursor/rules/— Cursor authoring/navigation rules -
package.json— scripts for dev/build/preview (VitePress 1.6.4) -
.github/workflows/— CI for GitHub Pages deploy
Notes
- Each series is independent: overview, prerequisites, chapters, and code live under its own folder.
- Sidebars are defined per-series in
docs/.vitepress/config.tsusing the directory layout above. - GitHub edit links point to
https://github.com/dalehurley/codewithphp/edit/main/docs/:path.
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 · 25 lines · 243 tokens per session scan A d6abc110e092
project-structure is a cursor rule published in the GitHub repository dalehurley/codewithphp (5 stars, last pushed 6mo ago), licensed MIT. It adds 243 tokens to every session, about $0.0012 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
generate-pr-description
This rule provides guidance for generating a pull request (PR) description in this repository.
bundling
The project uses a custom type bundling system to provide full TypeScript IntelliSense support in the Monaco editor for @bubblelab/bubble-core and its dependencies. This is necessary because Monaco cannot directly resolve workspace packages or external dependencies.
cursorrules
Root AI front door (this file). Depth: docs/AGENTS.md · Claude: docs/CLAUDE.md · Antigravity: docs/GEMINI.md · map: llms.txt Read first: docs/ai/INDEX.md → docs/ai/CANONICAL.md → docs/ai/COREREFERENCE.md Packages: docs/guides/ecosystem.md — GEMVC is a multi-package ecosystem (vendor/gemvc/). Core: gemvc/helper…
optimalize
SQL query optimization, index design, schema standards, and advanced SQL patterns for MySQL/MariaDB.
about-codebase
General information about the Lineai MCP Server codebase and its purpose.
general
API design standards — treat the API as a consumer-facing contract. Apply when designing, reviewing, or changing HTTP endpoints, routes, controllers, request/response payloads, and API resources.