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 commands/superuser-pal/awesome-second-brain/cotgit clone --depth 1 https://github.com/superuser-pal/awesome-second-brainWhat 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.00027 | $0.00248 |
| Opus 5 | $0.00014 | $0.00124 |
| Sonnet 5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
cot 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.
What it actually says
Inject Chain-of-Thought (CoT) reasoning into this session.
Steps
- Read
docs/strategies/cot.mdto load the strategy instructions. - Acknowledge the injection: "CoT strategy is now active. I'll think step by step for the remainder of this session."
- Apply the strategy's instruction text as a session-level addendum: for all subsequent responses that involve reasoning, analysis, or multi-step problem solving, think step by step before arriving at an answer.
- The strategy remains active until the user runs
/thinking:resetor activates a different strategy.
Notes
- CoT is the pre-promoted strategy — it is always available without needing to promote first.
- For other strategies, first run
/thinking:evalto see which active strategies fit your goal, then run/thinking:<slug>to inject one. - To clear:
/thinking:reset.
Source: [[docs/strategies/cot|Chain-of-Thought]] · [[docs/strategies/INDEX|Strategies Index]]
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.
- 2d ago First seen · 21 lines · 27 tokens per session scan A b92bd3795bc8
cot is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 248 once invoked, about $0.0001 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-30.
Other commands, from other repositories
canvas
AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.
ingest
Ingest a source (URL/file/text) into Raw Sources + compile 1015 Wiki pages, with mandatory user-purpose gate and mothership cross-linking.
audit
Audit the whole Wiki vault against 3 knowledge-integrity criteria — eligibility coverage, MOC-cluster consistency, confidence calibration. Produces a vault health report and queues high-priority pages for /verify.
verify
Verify a single Wiki page against 3 knowledge-integrity criteria — eligibility, consistency, confirmability. Writes verificationStatus back to the page; flags conflicts as disputed rather than deleting them.
lint
Run comprehensive wiki health check — orphans, broken links, contradictions, stale pages, index sync, MOC coverage, v2/v4/v5 frontmatter coverage, Core Context freshness, and cross-vault link integrity (mainVaultRelated/mainVaultCmds).
onboard
Interview-based first-run setup for this LLM Wiki kit. Asks the essential questions (vault location/name, Mode A/B, mothership path, Core Context identity + reuse axes), then fills every placeholder and writes Core Context so the wiki knows you from day one. Activate when the user says "온보딩해줘", "처음 시작할게", "처음 시작"…