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/SpillwaveSolutions/wiki_ticket_sddWrote 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/spillwavesolutions/wiki_ticket_sdd/second-brain)<a href="https://agentmods.dev/rules/spillwavesolutions/wiki_ticket_sdd/second-brain"><img src="https://agentmods.dev/badge/rules/spillwavesolutions/wiki_ticket_sdd/second-brain/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/spillwavesolutions/wiki_ticket_sdd/second-brain"><img src="https://agentmods.dev/badge/rules/spillwavesolutions/wiki_ticket_sdd/second-brain.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.00236 | $0.00236 |
| Opus 5.5 | $0.00094 | $0.00094 |
| Sonnet 5.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 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
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.
- 1mo 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 (11 stars, last pushed 25d ago), licensed MIT. It adds 236 tokens to every session, about $0.0009 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
shared-memory
Keep the shared project memory file up to date across all AI agents.
history-backfill
When onboarding an existing project, perform history backfill before normal steady-state memory maintenance.
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.
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.