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/spillwavesolutions/wiki_ticket_sdd/second-braingit clone --depth 1 https://github.com/SpillwaveSolutions/wiki_ticket_sddWhat 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 | $0.00236 | $0.00236 |
| Opus 5 | $0.00118 | $0.00118 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
second-brain 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 2d 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
You are recording work in WikiTicket SDD, a git-native append-only work log.
- Claim an identity first (
SECOND_BRAIN_IDENTITYor--actor/--author). - File the work in
.work/todo.jsonlviabin/worklogbefore doing it. - One session per worktree. Two assistants in one checkout switch branches under each other.
- Never hand-edit
.work/*.jsonlordocs/roadmap.md. The CLI appends;roadmap-renderregenerates. - Merge only when green (
gh pr merge --auto --merge). Never squash (ADR-0008). Never--admin. - Knowledge-tree (OKF) writes do not ship in this plugin. Use okf-plugin and second-brain-core. Do not invent a write path.
- Never name, link, or clone-instruct a private remote.
- Public samples stay Northstar / Lumenfield. No live client facts in public packs.
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.
- 2d ago First seen · 16 lines · 236 tokens per session scan A 846b18428891
second-brain is a cursor rule published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 2d ago), licensed MIT. It adds 236 tokens to every session, about $0.0012 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
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
pro-deck-builder
Create polished HTML slide decks and PDF-ready documents for consulting deliverables. Uses the RRBC design system with warm light mode, dark mode cover pages, Lora/Inter/Roboto Mono typography, and data visualization palette. Trigger on 'deck', 'slides', 'presentation', 'pitch deck', 'keynote', 'report', or 'PDF'.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
facebook-ads
Meta Ads (Facebook & Instagram) platform expertise. Audit campaigns, audiences, creative strategy, pixel tracking, and CAPI. Use when the user asks about Facebook Ads, Instagram Ads, Meta Ads, social media advertising, Advantage+ campaigns, or Meta pixel/CAPI setup.
paddle-integration
Conventions for Paddle integration code.
faststore-faststore-storefront-ref-project-structure-routes-and-config
FastStore project structure, routes, CLI build pipeline, store configuration (discovery.config.js), and naming conventions. Use when understanding how a FastStore project is organized, how the @faststore/cli works, what files to create or modify, how routing works, or how to configure store settings like SEO, API…