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/ai-supervisor-foundry/foundryWrote 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/ai-supervisor-foundry/foundry/contexts)<a href="https://agentmods.dev/rules/ai-supervisor-foundry/foundry/contexts"><img src="https://agentmods.dev/badge/rules/ai-supervisor-foundry/foundry/contexts/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/ai-supervisor-foundry/foundry/contexts"><img src="https://agentmods.dev/badge/rules/ai-supervisor-foundry/foundry/contexts.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.00005 | $0.00251 |
| Opus 5.5 | $0.00002 | $0.00100 |
| Sonnet 5.5 | $0.00001 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
contexts 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 Files (contexts/)
- Context files in
contexts/provide detailed project documentation for agents with zero context. - Read relevant context file before working on a project (e.g.,
contexts/easeclassifieds/frontend.mdfor FE work). - Context files contain project structure, recent fixes, configuration, and common issues.
- Update context files when making significant changes to keep them current.
- Use context files to quickly onboard new agents or understand project state.
Supervisor Context Files (supervisor-contexts/)
- Index: Read
supervisor-contexts/CONTEXT.mdfirst (<100 lines). It links to section files (overview, architecture, validation, usage, etc.). - Section files: Read specific files as needed (e.g.,
validation.md,tool-contracts.md). - Sliding Window: Check
supervisor-contexts/windows/for recent changes. - Usage: Use when working on the supervisor system itself (not project tasks).
- Updates: Window files are manually maintained—do not auto-generate.
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 · 21 lines · 5 tokens per session scan A 366a936c8c5a
contexts is a cursor rule published in the GitHub repository ai-supervisor-foundry/foundry (11 stars, last pushed 3mo ago), licensed MIT. It adds 5 tokens to every session and 251 once invoked, about $0.0000 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-09-02.
Other cursor rules, from other repositories
memory
USE WHEN working with Memoria memory tools - storing, retrieving, correcting, purging memories.
cursor-rules
Persistent memory across sessions via the bastra-recall MCP server — recall before acting, save durable rules and hard-won fixes.
relay
Relay coordination — room context, locks, /relay ask.
memory
A set of rules for recording reusable operational knowledge discovered during development, such as troubleshooting steps, environment requirements, and recurring setup problems.
jarvis-agent-rules
MCP server jarvis: notes, Jira, knowledge graph, sessions, preferences.
corivo
Corivo active memory integration.