linking-and-sources

Rules for linking tutorial chapters, series pages, code files, and external sources. They also cover GitHub editing links and licensing notes.

In plain words
What is it for?
Use them when writing Markdown links, referring to code stored beside chapters, linking to a series overview, or documenting sources and licensing.
Why use it?
They reduce broken navigation and make it clear where readers can find related chapters, runnable examples, and source information.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/dalehurley/codewithphp/linking-and-sources
Clone the repo
git clone --depth 1 https://github.com/dalehurley/codewithphp

Made for: Cursor.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,770 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.02770
Opus 5 $0.00006 $0.01385
Sonnet 5 $0.00003 $0.00554
Haiku 4.5 $0.00001 $0.00277

Measured 2d ago against content hash 2e8852c1f1e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

linking-and-sources 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.

.cursor/rules/linking-and-sources.mdc · 392 lines

How it starts

The opening of the file, as written. The whole thing — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Linking & Sources

Internal Linking

Chapter Links

  • Always use absolute paths from doc root for chapter links
  • Format: /series/<series-slug>/chapters/<nn>-<chapter-title>
  • Examples:
    • /series/php-basics/chapters/01-your-first-php-script
    • /series/ai-ml-php-developers/chapters/02-setting-up-your-ai-development-environment
See [Chapter 5: Your First ML Model](/series/ai-ml-php-developers/chapters/05-your-first-machine-learning-model-linear-regression-in-php) for the implementation.

Series Index Links

  • Link to series overview pages with absolute paths
  • Format: /series/<series-slug>/
Review the [PHP Basics series](/series/php-basics/) for foundational concepts.

Code Sample Links

From Chapter Markdown to Code Files

Use relative paths from the chapter file to the code directory:

::: info Code Examples
Complete, runnable examples are available in:

- [`verify-installation.php`](../code/chapter-02/verify-installation.php)
- [`test-phpml.php`](../code/chapter-02/test-phpml.php)
- [`test-rubixml.php`](../code/chapter-02/test-rubixml.php)
  :::

Pattern: ../code/<chapter-folder>/<filename>

Inline code references:

The complete implementation is in [`linear-regression.php`](../code/chapter-05/linear-regression.php).
From README to Code Files

Within a code directory's README, use relative paths:

- `verify-installation.php` - Comprehensive environment check
- `test-phpml.php` - PHP-ML library demonstration
- `solutions/exercise-1.php` - Solution to Exercise 1

Or for subdirectories:

See [`solutions/spam-filter-complete.php`](solutions/spam-filter-complete.php) for the full implementation.
Cursor Rule References (MDC Format)

When documenting code files in Cursor rules, use the mdc: format with full paths:

For Chapter 2, reference these files:

- [verify-installation.php](mdc:docs/series/ai-ml-php-developers/code/chapter-02/verify-installation.php) - Environment verification
- [test-phpml.php](mdc:docs/series/ai-ml-php-developers/code/chapter-02/test-phpml.php) - PHP-ML demonstration
- [composer.json](mdc:docs/series/ai-ml-php-developers/code/chapter-02/composer.json) - Dependencies

Read the full file on GitHub · 392 lines

Changes

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.

  1. 2d ago First seen · 392 lines · 13 tokens per session scan A 2e8852c1f1e8

Subscribe to this mod's changes

linking-and-sources is a cursor rule published in the GitHub repository dalehurley/codewithphp (5 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 2,770 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.