What is cross-linking?

A set of rules for linking completed work between progress.md, activeContext.md, tasks.md, and an archive document.

Use it after completing a task to add the required archive link, completion status, date, and next-focus reference in each specified file.

It keeps task status and completion records consistent across project-tracking files after a task is archived.

cross-linking — Cursor rule by kfnzero

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/kfnzero/mantis-mcp-server/cross-linking

Clone the repo

git clone --depth 1 https://github.com/kfnzero/mantis-mcp-server

Made for: Cursor.

Per session 888 This file is loaded in full into every session.

When invoked 888 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5	$0.00888	$0.00888
Opus 5	$0.00444	$0.00444
Sonnet 5	$0.00178	$0.00178
Haiku 4.5	$0.00089	$0.00089

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

Security

Grade A, and why

cross-linking 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

cross-linking — 100% identical, 0 lines differ

.cursor/rules/Core Implementation/cross-linking.mdc · 112 lines

How it starts

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

CROSS-LINKING REQUIREMENTS

TL;DR: After archiving a task, create specific cross-links in progress.md to reference the archive entry, update activeContext.md with the completion status, and mark the task as completed in tasks.md. Use the exact formats shown below.

🔗 CROSS-LINKING FORMATS

After completing and archiving a task, create these cross-links:

1️⃣ In progress.md:

## Completed Tasks
- [Task Name] - Completed on YYYY-MM-DD, see [archive entry](mdc:../docs/archive/completed_tasks.md#task-task-name-v10)

2️⃣ In activeContext.md:

## Recent Completions
- [Task Name] has been completed and archived. Next focus is on [Next Task].

3️⃣ In tasks.md:

## Completed Tasks
- [X] [Task Name] - Completed on YYYY-MM-DD

📝 FORMAT DETAILS

For progress.md:

Section title: ## Completed Tasks
Date format: YYYY-MM-DD
Link text: archive entry
Link format: mdc:../docs/archive/completed_tasks.md#task-task-name-v10
Anchor rules:
- Convert task name to lowercase
- Replace spaces with hyphens
- Add -v10 suffix (no parentheses or periods)
- NOTE: This should match format ## Task: Task Name v10 in archive

For activeContext.md:

Section title: ## Recent Completions
Format: [Task Name] has been completed and archived. Next focus is on [Next Task].
End with period
Use exact task names

For tasks.md:

Section title: ## Completed Tasks
Format: - [X] [Task Name] - Completed on YYYY-MM-DD
Use exact task names
Keep the [X] checkbox format

🔄 CROSS-LINKING PROCEDURE

Archive task in completed_tasks.md
Mark task as completed in tasks.md
Add entry to progress.md with link to archive
Update activeContext.md with completion status

✓ CROSS-LINKING CHECKLIST

Before completing any task, verify:

tasks.md shows task marked as [X] complete
progress.md contains link to archive entry with exact format
activeContext.md contains Recent Completions section with exact format
All links are valid and working
Task names match exactly between all files
Date format is YYYY-MM-DD
Link anchor format is correct (lowercase, hyphens, v10)

Read the full file on GitHub · 112 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.

2d ago First seen · 112 lines · 888 tokens per session scan A ce23163b68fa

Subscribe to this mod's changes

cross-linking is a cursor rule published in the GitHub repository kfnzero/mantis-mcp-server (10 stars, last pushed 12mo ago), licensed MIT. It adds 888 tokens to every session, about $0.0044 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.

Documents Planning

cross-linking