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 skills add nweii/agent-stuff --skill create-topic-notegit clone --depth 1 https://github.com/nweii/agent-stuffWrote 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/nweii/agent-stuff/create-topic-note)<a href="https://agentmods.dev/skills/nweii/agent-stuff/create-topic-note"><img src="https://agentmods.dev/badge/skills/nweii/agent-stuff/create-topic-note/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/skills/nweii/agent-stuff/create-topic-note"><img src="https://agentmods.dev/badge/skills/nweii/agent-stuff/create-topic-note.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.00049 | $0.00935 |
| Opus 5.5 | $0.00020 | $0.00374 |
| Sonnet 5.5 | $0.00010 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
create-topic-note 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 8d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create topic note
Create a topic note in Nathan's Brain vault that groups related notes under a common theme. Read the vault's AGENTS.md before accessing notes. Synthesize the provided notes into a lightweight hub.
Arguments
$ARGUMENTS should contain:
- Topic title (required) — name for the new topic note
- Notes to group — wikilinks or file paths to notes that share a theme
If no notes are provided, prompt for them. If no title is given but notes are provided, suggest a title based on the notes' common theme.
Process
1. Read the provided notes
Read each note's frontmatter (especially description) and skim content to understand:
- Common themes and concepts
- Shared vocabulary or framing
- The throughline that connects them
2. Expand context (optional)
Use available tools to discover additional relevant notes not explicitly provided:
- Semantic search — When qmd is available (MCP
querytool orqmd queryCLI), use it for semantic search —vecorexpandqueries that find notes by meaning rather than keywords. The qmd skill documents query types. For keyword search, use obsidian search or the methods below; qmd's lex/BM25 adds nothing beyond what obsidian already provides. - Follow wikilinks in the provided notes to find related children or siblings
- Check
relatedproperties for existing connections worth including - Search for shared tags or vocabulary
If you find notes that clearly belong under this topic, propose adding them to the group. Ask the user before including notes they didn't explicitly provide.
3. Create the topic note
Create a new file in 03-Records/Topics/ with this structure:
---
aliases:
- {alternative names if useful}
icon:
description: "{1-2 sentence summary synthesized from the grouped notes}"
related: []
tags: [index, {relevant topical tags, drawn from the grouped notes}]
---
{Optional 1-2 sentences of context if needed, otherwise leave blank}
![[Related.base]]
Description guidelines
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.
- 8d ago Changed · +1 lines 1f1ac1eded75
- 1mo ago First seen · 102 lines · 49 tokens per session scan A 9fe5dddd5976
create-topic-note is a skill published in the GitHub repository nweii/agent-stuff (10 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 935 once invoked, about $0.0002 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 skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.