second-brain

A set of rules for coding agents using WikiTicket SDD, a Git-based work log for recording development work. It defines how agents identify themselves, record tasks, work in a shared checkout, and merge changes.

In plain words
What is it for?
Use it to guide agents working with WikiTicket SDD, including task tracking, roadmap updates, shared worktrees, pull-request merging, and public documentation.
Why use it?
It ensures work is recorded before it starts and prevents agents from editing generated or append-only files by hand. It also sets rules for safe merging and for keeping private or client information out of public examples.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/spillwavesolutions/wiki_ticket_sdd/second-brain
Clone the repo
git clone --depth 1 https://github.com/SpillwaveSolutions/wiki_ticket_sdd

Made for: Cursor.

Per session 236 This file is loaded in full into every session.
When invoked 236 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 846b18428891, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.cursor/rules/second-brain.mdc · 16 lines

What it actually says

You are recording work in WikiTicket SDD, a git-native append-only work log.

  1. Claim an identity first (SECOND_BRAIN_IDENTITY or --actor / --author).
  2. File the work in .work/todo.jsonl via bin/worklog before doing it.
  3. One session per worktree. Two assistants in one checkout switch branches under each other.
  4. Never hand-edit .work/*.jsonl or docs/roadmap.md. The CLI appends; roadmap-render regenerates.
  5. Merge only when green (gh pr merge --auto --merge). Never squash (ADR-0008). Never --admin.
  6. Knowledge-tree (OKF) writes do not ship in this plugin. Use okf-plugin and second-brain-core. Do not invent a write path.
  7. Never name, link, or clone-instruct a private remote.
  8. Public samples stay Northstar / Lumenfield. No live client facts in public packs.
Changes

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.

  1. 2d ago First seen · 16 lines · 236 tokens per session scan A 846b18428891

Subscribe to this mod's changes

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.

Related

Other cursor rules, from other repositories

cursor

You are working on the checkout service. Preserve transaction integrity and auditability.

mrwogu/promptscript · 53 tokens

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'.

thatrebeccarae/claude-marketing · 70 tokens

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.

thatrebeccarae/claude-marketing · 50 tokens

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.

thatrebeccarae/claude-marketing · 55 tokens

paddle-integration

Conventions for Paddle integration code.

PaddleHQ/paddle-agent-skills · 380 tokens

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…

vtex/skills · 70 tokens