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/zongmin-yu/serenity-skillsWrote 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/zongmin-yu/serenity-skills/serenity-guidelines)<a href="https://agentmods.dev/rules/zongmin-yu/serenity-skills/serenity-guidelines"><img src="https://agentmods.dev/badge/rules/zongmin-yu/serenity-skills/serenity-guidelines/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/zongmin-yu/serenity-skills/serenity-guidelines"><img src="https://agentmods.dev/badge/rules/zongmin-yu/serenity-skills/serenity-guidelines.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.00044 | $0.00790 |
| Opus 5 | $0.00022 | $0.00395 |
| Sonnet 5 | $0.00009 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
serenity-guidelines 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 11d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Serenity Guidelines
AI infrastructure and semiconductor supply chain analysis, distilled from the public posts of Serenity (@aleabitoreddit).
When trillions flow into AI buildout, some tiny company with no substitutes will be the bottleneck. Trace the capex from hyperscalers down through semiconductors, photonics, materials, and feedstock to find it before the market does.
Quick Filter
Run these first. Two "No" answers means this is probably not a chokepoint.
| # | Principle | Question | No = Stop |
|---|---|---|---|
| 1 | Forced Demand | Is someone forced to buy this input to ship their product? | No forced buyer = no chokepoint |
| 2 | Size Mismatch | Is the supplier's market cap < 1% of the annual capex it enables? | No mismatch = probably priced in |
| 3 | No Substitute | Is there no production-ready alternative within 24 months? | Substitute in qualification = expiring chokepoint |
| 4 | Outside Voice | Have ≥ 3 independent parties confirmed the constraint in 90 days? | Nobody else sees it = too early or wrong |
Process (after passing the filter)
- Follow the Money — Where is capex flowing? Which layer is heating up? (Also valid: enter from a geopolitical event or policy action that forces supply chain restructuring.)
- Decompose the BOM — Break down the product. Which components take the largest cost share? (If BOM is not public, reconstruct from known supplier relationships + analyst reports + community intelligence.)
- Who Makes It? — Count suppliers. How many can make this at required quality and volume?
- Find the Monopoly — Supplier count ≤ 3 + small MC + high switching costs = chokepoint. (If upstream producers are large oligopolies, go one layer above to the smaller equipment/testing/controller companies they depend on.)
- Verify Irreplaceability — Check substitutes. Qualification cycle? Capacity ramp timeline? (For early architecture transitions: qualification progress > trailing revenue.)
- Go Deeper — Who supplies the supplier? Bottleneck within the bottleneck?
- Historical Pricing — Similar scarce materials spiked how much? Cost of project delay?
- External Validation — Earnings calls, analyst coverage, policy actions, combat/deployment validation?
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.
- 11d ago First seen · 50 lines · 44 tokens per session scan A 58e121680cd8
serenity-guidelines is a cursor rule published in the GitHub repository zongmin-yu/serenity-skills (34 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 790 once invoked, about $0.0002 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-30.
Other cursor rules, from other repositories
tensorflow
TensorFlow: Keras, model training, production deployment.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.