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 skills/imtylerrrrrr/second-brain/analyzenpx skills add Imtylerrrrrr/second-brain --skill analyzegit clone --depth 1 https://github.com/Imtylerrrrrr/second-brainWrote 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/skills/imtylerrrrrr/second-brain/analyze)<a href="https://agentmods.dev/skills/imtylerrrrrr/second-brain/analyze"><img src="https://agentmods.dev/badge/skills/imtylerrrrrr/second-brain/analyze.svg" alt="Measured on agentmods" 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 | $0.00061 | $0.00541 |
| Opus 5 | $0.00030 | $0.00270 |
| Sonnet 5 | $0.00012 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
analyze 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 4d 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
second-brain: analyze
The evidence engine. Follow the discipline below EXACTLY — Part 2 governs this skill.
!cat "${CLAUDE_PLUGIN_ROOT}/references/discipline.md"
Steps
- Locate the vault (cwd or ancestors containing
Projects/Dashboard.md; else registered vaults in~/.claude/second-brain/vaults, ask if several; none → "run /second-brain:setup first"). Resolve the repo: the argument, else cwd, else ask. Locate its note in<vault>/Projects/by frontmatterrepo:match; missing → create fromProjects/_TEMPLATE.md; auto-stub → this is an onboarding run. - Read the evidence, in Part 2 order: README/docs → manifest → source tree → tests (run them only if cheap and safe — a test suite, not a deploy) →
git -C <repo> log --oneline -30→ open PRs/issues viaghif available. - Write the note:
## 📌 One-linerfrom what the code actually is.## 🏁 Milestoneswith cited marks per Part 2 ([x]artifact+tests/commit ·[~]partial, cite present AND missing ·[ ] needs check).- Claims-vs-evidence contradictions recorded explicitly (e.g. "README claims billing ready;
src/billing/stripe.tsis a stub with 0 tests → [~]"). - frontmatter
status+last_updated. Do NOT touch## ▶ Threadorlast_handoff_commit.
- Resolve TODO verification tasks left by end-session (
confirm milestone "…"): verify each against evidence, mark the milestone accordingly with its citation, remove the TODO line. - Update the Dashboard row: Status · Updated (fill Last session/Next only if the columns are empty — they belong to end-session).
- Report: what the evidence showed, every correction made, contradictions found — and invite the user to correct anything inferred.
Rules
- Every mark cites evidence inline. No percentages. Code beats docs. Unknown → needs check. Never write to
## ▶ Thread.
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.
- 4d ago First seen · 27 lines · 61 tokens per session scan A d53ecea794d8
analyze is a skill published in the GitHub repository Imtylerrrrrr/second-brain (1 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 541 once invoked, about $0.0003 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 skills, from other repositories
s-continue
Cheaper and faster than /compact. Restores previous session context from Claude Code AND Codex transcripts by reading them directly — no LLM calls, no token cost. Also auto-loads a handoff written by /s-compact, if one exists. Triggers on "s-continue", "restore context", "what was I doing", "pick up where I left off"…
s-compact
Session handoff for the next session — write-side pair of /s-continue. Triggers on "s-compact", "session handoff", "handoff prompt", "hand off", "wrap up the session", "prep for next session". Distills what /s-continue cannot recover: subagent findings, tool-output numbers, and decisions that never entered the…
usage-view
Know exactly what you spent (Claude Code) or how much of your Codex limit you have used (Codex). Interactive HTML dashboard with token usage and, on Claude Code, cost breakdown and 5-hour window timeline across all sessions.
report-limit
Max plan hit the wall? Report your 5h window data — we're mapping the rate limit formula Anthropic won't publish.
setup-statusline
Live token counter in your CLI. Shows real-time input/output/cache token counts in the Claude Code status bar.
setup-git-lite
Disable Claude Code built-in git instructions and inject a curated 280-tok minimum via SessionStart hook. Saves 2,200 tok/session + 1,700 tok/call.