Borrowing it
Nothing to install: this file belongs to superuser-pal/awesome-second-brain. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/superuser-pal/awesome-second-brain/main/.claude/commands/capture/quick-dump.mdgit clone --depth 1 https://github.com/superuser-pal/awesome-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/commands/superuser-pal/awesome-second-brain/quick-dump)<a href="https://agentmods.dev/commands/superuser-pal/awesome-second-brain/quick-dump"><img src="https://agentmods.dev/badge/commands/superuser-pal/awesome-second-brain/quick-dump/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/commands/superuser-pal/awesome-second-brain/quick-dump"><img src="https://agentmods.dev/badge/commands/superuser-pal/awesome-second-brain/quick-dump.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.00033 | $0.00741 |
| Opus 5.5 | $0.00013 | $0.00296 |
| Sonnet 5.5 | $0.00007 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
quick-dump 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 2mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Dump
Process the following freeform dump.
Usage
/quick-dump <content>
Routing note: This command is for high-confidence routing. It bypasses the three-stage inbox pipeline and routes directly to final destinations (domains, work pages, or thinking notes).
For each distinct piece of information:
-
Classify it: decision, incident, 1-on-1 content, win/achievement, architecture, project update, person context, or general work note.
-
Check for split-worthy content — If the dump covers 3+ independently page-worthy topics (each self-contained and useful on its own), offer to split before routing:
This dump covers [N] independent topics: 1. [Topic A] → suggested page: `topic-a.md` 2. [Topic B] → suggested page: `topic-b.md` Split into separate pages, or route as one?Only split if topics are genuinely separable — not if they build on each other.
-
Search first: Use
qmdsemantic search (orobsidian search) to check if a related page already exists. Prefer appending to existing pages over creating new ones for small updates. -
Preserve original source — When creating a new page, include the verbatim raw input in a collapsible callout at the bottom:
> [!quote]- Original Source > [raw input exactly as provided, no formatting changes] -
Create or update the appropriate page following CLAUDE.md conventions:
- Correct folder placement:
domains/[Name]/02_PAGES/orwork/04_PAGES/→ becomes a page;thinking/→ remains a note withstatus: thinking - Full YAML frontmatter with date, description, tags, and type-specific fields
- All relevant [[wikilinks]] to people, projects, teams, competencies
- Correct folder placement:
-
Update indexes as needed (work/INDEX.md, work/05_REVIEW/WINS.md, work/06_ORG/PEOPLE.md)
-
Cross-link: Ensure every new page links to at least one existing page or note and is linked FROM at least one existing page.
-
Cascade updates — After the primary page is placed, enrich related existing pages:
- Use
qmdto find 3-5 most related existing pages. - For each related page: wikilink additions, content appends (on confirmation), or contradiction flags.
- Use
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.
- 2mo ago First seen · 68 lines · 33 tokens per session scan A 62fe9a3ee19a
quick-dump is a command published in the GitHub repository superuser-pal/awesome-second-brain (16 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 741 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 commands, from other repositories
onboard
An interview-based setup command for an LLM Wiki, a notes system designed for use with language models. It asks about your wiki, files, working mode, and personal context, then fills in the setup details.
refresh-context
Re-snapshot Core Context.md from (optional) mothership system files + key personal essays. Run when mothership files change, when new essays signal philosophy shift, or when snapshot is older than 30 days.
session-learn
Extract knowledge from the current session. Invoke with /session-learn or "extract this session".
status
Show memex statistics and status including projects, memos, and pending items.
curate
A command for maintaining a file-based knowledge wiki. It can review pages, shorten overlong material, manage page lifecycles, find possible contradictions, and rebuild weak connections between notes.
ingest
A command for adding information to a file-based knowledge wiki from web pages, files, or text notes. It classifies the material, updates or creates wiki pages, and adds links between related pages.