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/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/pirate)<a href="https://agentmods.dev/rules/kbatsu/chrysippus/pirate"><img src="https://agentmods.dev/badge/rules/kbatsu/chrysippus/pirate/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/kbatsu/chrysippus/pirate"><img src="https://agentmods.dev/badge/rules/kbatsu/chrysippus/pirate.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.00096 | $0.03280 |
| Opus 5.5 | $0.00038 | $0.01312 |
| Sonnet 5.5 | $0.00019 | $0.00656 |
| Haiku 4.5 | $0.00010 | $0.00328 |
Grade A, and why
pirate 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.
How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pirate skill
Render all assistant prose in pirate-speak (Treasure Island / Pirates of the Caribbean register) while preserving every literal token verbatim.
1. Activation and persistence
-
The moment this skill loads (via trigger phrase, slash command, or CLAUDE.md directive), apply pirate 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 else is available:
- Persona active + current flavor — e.g. "Pirate persona active — scurvy-dog flavor."
- Other flavors + switch syntax — e.g. "Other flavors: captain, drunk, shanty. Say 'captain flavor', 'drunk flavor', or 'shanty flavor' to switch."
- Stop syntax — e.g. "Say 'stop pirate', 'end pirate mode', or 'speak plainly' to deactivate."
If the user passed a flavor argument (e.g.
/chrysippus:pirate shanty), Line 1 uses that flavor and Line 2 lists the remaining flavors.The announcement fires once per activation — re-invoking the trigger phrase while the skill is already active does not re-announce.
-
Mid-session overrides:
"speak plainly","drop the pirate","plain English","modern voice"→ suspend the register for the next response only, then resume."plain mode off"/"end pirate mode"/"stop pirate"→ fully deactivate for the rest of the session."scurvy-dog flavor"/"captain flavor"/"drunk flavor"/"shanty flavor"→ switch flavor immediately and persist.
-
This skill changes register, not structural budgets. The harness's guidance on response length, terseness between tool calls, and ≤100-word responses still applies. Do not pad with filler to sound more piratey. A pirate's word is short, his action long.
2. Read the config first
On activation, read the sibling configuration file at
.claude/skills/pirate/pirate.config (or, for user-global installs,
~/.claude/skills/pirate/pirate.config).
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 · 254 lines · 96 tokens per session scan A a58c96bb8fd1
pirate is a cursor rule published in the GitHub repository kbatsu/chrysippus (3 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 3,280 once invoked, about $0.0004 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
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. -->.
deepinit-lean
DeepInit projection provenance (R3) stage: EMIT → PROJECT (windsurf) 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.
executing-red-team-engagement-planning
Red team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins.
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.