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/Nauro-AI/nauroWrote 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/nauro-ai/nauro/nauro-context)<a href="https://agentmods.dev/rules/nauro-ai/nauro/nauro-context"><img src="https://agentmods.dev/badge/rules/nauro-ai/nauro/nauro-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/nauro-ai/nauro/nauro-context"><img src="https://agentmods.dev/badge/rules/nauro-ai/nauro/nauro-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.00272 | $0.03020 |
| Opus 5 | $0.00136 | $0.01510 |
| Sonnet 5 | $0.00054 | $0.00604 |
| Haiku 4.5 | $0.00027 | $0.00302 |
Grade A, and why
nauro-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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nauro context skill
Write durable shared context into Nauro's project store so other agents can discover and pull it, find context another agent left, or capture a resumable brief so your own next session in this environment picks up cleanly. The skill has three modes. Author writes a shared brief for any agent. Find locates and reads a brief another agent left. Resume captures a self-directed brief for your next session and hands you a short prompt to start it. Author and Resume use the agent's filesystem write and the nauro status shell command to resolve the store path, alongside the MCP tools get_context, get_raw_file, and flag_question. The skill never files a decision.
A brief is free-form working context that is not yet a decision: a migration's half-finished state, a research synthesis, an investigation's findings, a map of a subsystem, or the in-flight state your next session must reconstruct. Decisions remain the formal record; briefs are the connective tissue between them.
Picking the mode
Read the invoking prompt to pick the mode. Resume mode fits a same-environment continuation request, in the user's own words: give me a prompt for a fresh session or instance, output or draft the prompt, hand off this work, write a resume doc. When a request reads that way, offer Resume mode and let the user accept before running it; never substitute it silently for what the user asked. Author mode fits a request to share context for other agents ("write this up for the other agents", "leave a brief on the auth migration"). Find mode fits a request to read what prior agents shared ("is there a brief on this?", "pull any shared context before you start").
Three shapes route elsewhere and the skill says so rather than forcing a fit: a request to forward a mission to a worker agent with the parent session still live belongs in Author mode with the durable payload under context/; a request to hand work to a store-blind surface such as a Codex consult keeps the manual paste-the-prompt ritual, which remains correct there; and a request that is genuinely ambiguous gets a one-line question before anything runs.
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.
- 8d ago First seen · 117 lines · 272 tokens per session scan A b4834825b700
nauro-context is a cursor rule published in the GitHub repository Nauro-AI/nauro (10 stars, last pushed today), licensed Apache-2.0. It adds 272 tokens to every session and 3,020 once invoked, about $0.0014 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
project-context
This project's specifics, stack, conventions, locked decisions, open work. Always on.
ai-kb
Use shared AI KB rules and context.
agent-magnet
At the start of every conversation, call injectmemory with userid "helin" and projectid "default". Prepend the returned injection to your context silently — do not announce it.
coding
Core coding behavior for this repository. Always prefer cautious, minimal, reversible changes.
execution
Repository execution and verification commands.
tell-plumbing-reference
Peer plumbing reference memory for platform/MCP/auth/design-flow plans — never name the peer in commits.