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.
git clone --depth 1 https://github.com/novoads/agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/novoads/agent-skills/project-context)<a href="https://agentmods.dev/rules/novoads/agent-skills/project-context"><img src="https://agentmods.dev/badge/rules/novoads/agent-skills/project-context/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/novoads/agent-skills/project-context"><img src="https://agentmods.dev/badge/rules/novoads/agent-skills/project-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00466 | $0.00466 |
| Opus 5.5 | $0.00186 | $0.00186 |
| Sonnet 5.5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
project-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 1mo 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
Project context
- If
.envorMASTER_CONTEXT.mddo not exist, tell the user to run./scripts/setup.sh. - At the start of substantive work in this repo, read MASTER_CONTEXT.md at the repository root for brand voice, default product, and API learnings. It carries no prices — that is deliberate.
- The first time the user asks to generate something and
MASTER_CONTEXT.mdis missing a field that request needs (default product, brand voice), ask for it then — once — and write the answer back so no future session asks again. A setup-only session asks for nothing and reports almost nothing: close with the setup-close template inAGENTS.md("First-time setup" — a status line, "What you can ask for now", the product-photos line) and keep git mechanics and sync details out unless they block an ask. Never write a credit number into it. - After significant changes (new workflows, verified Novoads behaviors, brand updates), append a short dated entry to the Changelog section in MASTER_CONTEXT.md.
- For Novoads HTTP usage, prompts, and polling, follow
.cursor/skills/novoads-api/SKILL.mdand linked reference.md. - Session work-product goes in a gitignored home —
generated/(renders),outputs/<job>/(video downloads + edit workfiles),prompts/(composed prompts),iterations/(clone rounds),logs/. Never invent a new top-level directory; leavegit statusas clean as you found it. Stated in full inAGENTS.md("Every session"). - Never quote a credit cost from memory. Prices come from a live
POST /v1/estimatesin the current session, shown and approved before anything is generated. For a video where the model speaks, the spoken line is approved separately, first. - Log every generation call to
logs/novoads-api.jsonl— observability only, never a pricing source.
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.
- 1mo ago First seen · 16 lines · 466 tokens per session scan A 73f6dbab1c4e
project-context is a cursor rule published in the GitHub repository novoads/agent-skills (24 stars, last pushed yesterday), licensed MIT. It adds 466 tokens to every session, about $0.0019 per session on Opus 5.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
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.