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/AKSoftCode/aicrewWrote 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/aksoftcode/aicrew/karpathy-guardrails)<a href="https://agentmods.dev/rules/aksoftcode/aicrew/karpathy-guardrails"><img src="https://agentmods.dev/badge/rules/aksoftcode/aicrew/karpathy-guardrails/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/aksoftcode/aicrew/karpathy-guardrails"><img src="https://agentmods.dev/badge/rules/aksoftcode/aicrew/karpathy-guardrails.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.00194 | $0.00194 |
| Opus 5.5 | $0.00078 | $0.00078 |
| Sonnet 5.5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
karpathy-guardrails 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
Karpathy Guardrails
Apply these four principles to every code change in this project.
Full agent spec: ~/Agents/agents/karpathy-guardrails.md
1. Think Before Coding
State the goal in one sentence before touching any file. Identify the entry point, call chain, and files that will change.
2. Simplicity First
Prefer fewer files, fewer abstractions, shortest path to passing tests. No new dependencies unless confirmed necessary.
3. Surgical Changes
Change only what is required for the goal. Do not reformat, rename, or touch code outside the affected region.
4. Goal-Driven Execution
Every edit traces back to the stated goal. Stop when the acceptance criterion is met. Do not gold-plate.
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 · 27 lines · 194 tokens per session scan A fc8f462cabb3
karpathy-guardrails is a cursor rule published in the GitHub repository AKSoftCode/aicrew (3 stars, last pushed 3mo ago), licensed MIT. It adds 194 tokens to every session, about $0.0008 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
cursorrules
You are connected to krusch-context-mcp, a persistent working memory engine. You MUST follow this lifecycle protocol across all coding sessions.
project
Core project context for ai-context-kit.
ult-autoscaffold-content
Generate real starter content for a project's What-L2 (requirements) and How-L2 (architecture/conventions) CEP layers once ult-repo-layout has resolved their paths but found them empty — an honest, minimal, YAML-frontmatter-first overview document per layer for small/single targets, or graphify-informed per-module…
ult-onboarding-index
Discover CEP-managed content already present in a target repo (What/How layer docs, compiled guidelines, context packages, decision ledger) via existence checks against layout-slots-registry.yaml-resolved paths, then write one canonical root AGENTS.md onboarding index plus thin per-tool pointer stubs…
x-harness
Use only light, standard, deep. Do not use small, medium, large.
demo-write-user-stories
Reference implementation that writes functional user stories from a feature description, optionally grounded in an approved CEP context package per CONSUMING-CONTEXT-PACKAGE.md, with per-story citations and the standard tag/reverse-index loop. A worked example for downstream teams building their own context-consuming…