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/linkpranay-ai/context-engineering-protocol/compiling-project-guidelinesgit clone --depth 1 https://github.com/linkpranay-ai/context-engineering-protocolWhat 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.00037 | $0.00095 |
| Opus 5 | $0.00018 | $0.00048 |
| Sonnet 5 | $0.00007 | $0.00019 |
| Haiku 4.5 | $0.00004 | $0.00010 |
Grade A, and why
compiling-project-guidelines 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
Compiling Project Guidelines
This repository packages its capabilities as portable skills for AI
coding agents. Read .github/skills/compiling-project-guidelines/SKILL.md and follow it
when this rule applies.
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 · 12 lines · 37 tokens per session scan A 0cb5d65fe124
compiling-project-guidelines is a cursor rule published in the GitHub repository linkpranay-ai/context-engineering-protocol (8 stars, last pushed 3d ago), licensed Apache-2.0. It adds 37 tokens to every session and 95 once invoked, about $0.0002 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
x-harness
Use only light, standard, deep. Do not use small, medium, large.
ai-dev-os-init
AI Dev OS initial setup wizard. Use when starting a new project or introducing AI Dev OS. Asks about the project's tech stack and scale, then generates an optimal 4-layer structure from templates.
ai-dev-os-audit
Audits the health of the AI Dev OS 4-layer structure. Detects dependency rule violations, expiration, and coverage gaps. Used for monthly or quarterly periodic maintenance.
ai-dev-os-extract
Extracts rules from the gap between AI-generated code and ideal code. Used after code review to add new rules to AI Dev OS guidelines. A Rule Harvesting approach to rule discovery.
ai-dev-os-report
Generates an AI Dev OS compliance report for teams and stakeholders. Includes compliance rate trends, major violations, and improvement proposals for a specified period. Used for weekly or monthly reporting.
ai-dev-os-why
Explains the "why" behind a specific AI Dev OS rule or guideline. Traces the path from L3 guideline → L2 principle → L1 philosophy. Used when team members question a rule.