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/project-archivegit 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/project-archive)<a href="https://agentmods.dev/commands/superuser-pal/awesome-second-brain/project-archive"><img src="https://agentmods.dev/badge/commands/superuser-pal/awesome-second-brain/project-archive.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.00000 | $0.00351 |
| Opus 5 | $0.00000 | $0.00176 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
project-archive 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 5d 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
Project Archive
Move a completed project from work/01_PROJECTS/ to work/07_ARCHIVE/YYYY/ and update all indexes.
Usage
/project-archive <project name>
Workflow
1. Find the Note
Search work/01_PROJECTS/ for the project name. Confirm with the user before proceeding.
2. Update Frontmatter
- Set
status: completed - Verify
quarterproperty is set correctly - Verify
descriptionreflects the final state
3. Move the File
git mv "work/01_PROJECTS/<Note>.md" "work/07_ARCHIVE/YYYY/"
Use the year from the note's date field.
4. Update Indexes
work/INDEX.md: Move from Active Projects to the appropriate Completed quarter sectionbrain/NORTH_STAR.md: Mark as completed in Current Focus if listed therework/05_REVIEW/WINS.md: Verify the project is captured in the relevant quarter sectionbrain/MEMORIES.md: Update Recent Context if the project is mentioned as "in progress"
5. Verify
- Run a quick check that no wikilinks are broken (Obsidian resolves by name, so moves shouldn't break links)
- Confirm the Work Dashboard Base shows the note in "Completed" view, not "Active Work"
Important
- Always use
git mv— never copy+delete - Don't archive without user confirmation
- If the project has related incident notes, ask if those should be updated too
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.
- 5d ago First seen · 48 lines · 0 tokens per session scan A f71cdc8195ec
project-archive is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 351 tokens. 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 "온보딩해줘", "처음 시작할게", "처음 시작"…