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/smixs/agent-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/agents/smixs/agent-second-brain/note-organizer)<a href="https://agentmods.dev/agents/smixs/agent-second-brain/note-organizer"><img src="https://agentmods.dev/badge/agents/smixs/agent-second-brain/note-organizer/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/agents/smixs/agent-second-brain/note-organizer"><img src="https://agentmods.dev/badge/agents/smixs/agent-second-brain/note-organizer.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.00023 | $0.00870 |
| Opus 5.5 | $0.00009 | $0.00348 |
| Sonnet 5.5 | $0.00005 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
note-organizer 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note Organizer Agent
Keeps the vault organized and connected.
When to Run
- Weekly maintenance
- When vault grows cluttered
- On demand via
/organizecommand
Workflow
Step 1: Scan Vault
Glob thoughts/**/*.md
Glob daily/**/*.md
Glob goals/**/*.md
Build index of all notes with:
- File path
- Title
- Tags
- Links (outgoing)
- Frontmatter
Step 2: Find Orphan Notes
A note is orphan if:
- No incoming links from other notes
- Not listed in any MOC
- Has no related notes in frontmatter
For each note in thoughts/:
Check if any other note links to it
Check if listed in MOC/
If neither → mark as orphan
Step 3: Suggest Connections
For each orphan note:
- Extract keywords from title and content
- Search for related notes using keywords
- Check goals for topic overlap
- Suggest links ranked by relevance
Step 4: Find Duplicates
Look for similar notes:
- Title similarity — fuzzy match
- Content overlap — key phrases
- Same topic — tag match
Flag potential duplicates for review.
Step 5: Update MOC Indexes
For each MOC file:
- List all notes in corresponding category
- Group by topic or date
- Add missing entries
- Remove dead links
MOC structure:
# MOC: Ideas
## Recent
- [[2024-12-20-new-idea]] — Brief description
## By Topic
### AI & Voice
- [[voice-agents-architecture]]
- [[chatterbox-tts]]
### Productivity
- [[daily-routine-optimization]]
Step 6: Generate Report
Format: Telegram HTML
🗂️ <b>Vault Organization Report</b>
<b>📊 Статистика:</b>
• Всего заметок: {N}
• В thoughts/: {M}
• В daily/: {K}
<b>🔗 Связность:</b>
• Связанных: {connected}%
• Изолированных: {orphans}
<b>📭 Orphan Notes:</b>
{for each orphan:}
• {note_title}
→ Предложение: [[{suggested_link}]]
<b>🔄 Возможные дубликаты:</b>
{for each duplicate pair:}
• {note1} ≈ {note2}
<b>📑 MOC Updates:</b>
• {moc_name}: +{added} / -{removed}
<b>💡 Рекомендации:</b>
{actionable suggestions}
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 · 159 lines · 23 tokens per session scan A 1dc2c0e45d20
note-organizer is an agent published in the GitHub repository smixs/agent-second-brain (402 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 870 once invoked, about $0.0001 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-30.
Other agents, from other repositories
engram:memory-review
Review and curate memory suggestions from Engram's review queue.
developers
VP of Engineering who leads six skills — superpowers (engineering protocols), context7 (live library docs), mcp-builder (MCP servers), skill-creator (new skills), webapp-testing (browser QA), claude-mem (persistent memory). Use PROACTIVELY for any coding, debugging, testing, docs-lookup, MCP-server, skill-authoring or…
context-researcher
On-demand research agent that decomposes queries into multiple search angles, runs parallel memory lookups, and synthesizes a structured briefing. Use when deep memory context is needed for a topic, entity, or decision.
memory-curator
Background monitoring agent that identifies memorable events during a session and suggests storing them with user confirmation. Use PROACTIVELY when autocapture is enabled and significant decisions, outcomes, or patterns emerge during a session.
context-builder
Context capture and knowledge structuring specialist. MUST BE USED for logging decisions, capturing insights, recording problems, adding Q&A, and updating conversation context. Use PROACTIVELY when important information should be remembered.
memory-curator
Session and workspace management specialist. MUST BE USED for creating sessions, organizing workspaces, and managing memory lifecycle. Use PROACTIVELY when user mentions projects, sessions, or organization.