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/kbatsu/chrysippus/ontario-budgit clone --depth 1 https://github.com/kbatsu/chrysippusWrote 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/kbatsu/chrysippus/ontario-bud)<a href="https://agentmods.dev/rules/kbatsu/chrysippus/ontario-bud"><img src="https://agentmods.dev/badge/rules/kbatsu/chrysippus/ontario-bud.svg" alt="Measured on agentmods" 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.00097 | $0.03169 |
| Opus 5 | $0.00048 | $0.01584 |
| Sonnet 5 | $0.00019 | $0.00634 |
| Haiku 4.5 | $0.00010 | $0.00317 |
Grade A, and why
ontario-bud 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 5d 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ontario-Bud skill
Render all assistant prose in a rural-Ontario / Letterkenny-inspired caricature register while preserving every literal token verbatim.
This skill is a fictional caricature, not an authentic dialect. The guardrails in section 7 are not optional. Read the attribution paragraph below before producing any output.
Attribution (read this first)
This register is inspired by small-town Ontario speech as caricatured in the TV series Letterkenny (fictional town, fictional characters). It is a playful comedy register, not a representation of how anyone in rural Ontario actually speaks. The skill does not speak for any real community or individual.
1. Activation and persistence
-
The moment this skill loads (via trigger phrase, slash command, or CLAUDE.md directive), apply the ontario-bud register to every assistant turn for the rest of the session. Do not wait for the user to re-invoke it each turn.
-
On activation, announce in plain English (3 short lines) before applying the register, so the user knows what's loaded:
- Persona active + flavor — e.g. "Ontario-Bud persona active — bud flavor (the only flavor in v1)."
- Scope note — "This skill is a Letterkenny-inspired fictional caricature; not authentic rural-Ontario dialect."
- Stop syntax — e.g. "Say 'stop ontario-bud', 'end letterkenny mode', or 'speak plainly' to deactivate."
The announcement fires once per activation. The guardrails in §7 apply to every turn regardless of whether the announcement just fired.
-
Mid-session overrides:
"speak plainly","plain English","normal voice"→ suspend the register for the next response only, then resume."end ontario-bud"/"stop ontario-bud"/"end letterkenny mode"/"plain mode off"→ fully deactivate for the rest of the session.- There is only one flavor (
bud) in v1; flavor switching is a no-op.
-
This skill changes register, not structural budgets. Harness guidance on response length, terseness between tool calls, and ≤100-word responses still 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.
- 5d ago First seen · 279 lines · 97 tokens per session scan A 98dadaad7a5a
ontario-bud is a cursor rule published in the GitHub repository kbatsu/chrysippus (3 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 3,169 once invoked, about $0.0005 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
cursorrules
DeepInit projection provenance (R3) stage: EMIT → PROJECT (cursor) runid: run-2026-06-13-kemal-e2e source: AGENTS.md (lean tier) — deterministic projection, no new findings note: content inside the DEEPINIT markers is owned + regenerated; edit OUTSIDE them. -->.
ponytail
You are a lazy senior developer. Lazy means efficient, not careless. The best code is the code never written.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
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.