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/lineage-foundation/mcp/plans_for_contextgit clone --depth 1 https://github.com/lineage-foundation/mcpWhat 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.00244 | $0.00244 |
| Opus 5 | $0.00122 | $0.00122 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
plans_for_context 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.
What it actually says
The /plans directory contains a masterplan.md and step plans for each task.
Always reference these plans for project context.
Plan-writing guidance (concise):
- Guidance-first: describe steps and intent; avoid full file contents or long code blocks.
- Minimal commands: include only essential commands (e.g.,
uvinstalls, run/test) for clarity. - Structure: use Phase sections (e.g., Tooling & Architecture; Abstract Execution Protocol) with Purpose and Action bullets.
- References: cite official docs/links relevant to the step (MCP, transports, SDKs).
- References: cite official docs/links relevant to the step (MCP, transports, SDKs, Railway railpack).
- Dependencies: list package names; avoid pinning unless necessary; dev extras grouped per step.
- Environment: follow 12‑factor; provide
.env.exampleguidance (no secrets in plans). - Deployment: include minimal guidance for
railpack.json(install withuv sync, start withuv run uvicorn ... --port $PORT). - Security & errors: note privileged ops and error conventions at spec level; implement later.
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 · 16 lines · 244 tokens per session scan A 80f0e7bad5b9
plans_for_context is a cursor rule published in the GitHub repository lineage-foundation/mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 244 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.