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/rituals/week-close.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/week-close)<a href="https://agentmods.dev/commands/superuser-pal/awesome-second-brain/week-close"><img src="https://agentmods.dev/badge/commands/superuser-pal/awesome-second-brain/week-close/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/week-close"><img src="https://agentmods.dev/badge/commands/superuser-pal/awesome-second-brain/week-close.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.00022 | $0.00607 |
| Opus 5.5 | $0.00009 | $0.00243 |
| Sonnet 5.5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
week-close 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the weekly-closing workflow from the daily-rituals skill.
- Load the active week file from
plan/ - Calculate velocity (completed / planned)
- Weekly Synthesis: Perform cross-session analysis (patterns, wins, North Star)
- Handle each incomplete task: carry forward, backlog, drop, or pause
- Gather retrospective (what went well, what to change)
- Consolidate daily notes and archive to
plan/archive/
7. Domain Cluster Detection + Pulse
After the daily-rituals workflow completes, run a condensed version of the audit cluster detection and pulse:
Cluster Detection (same logic as /audit §12a, condensed):
- For each domain, count flat pages in
02_PAGES/by navigation type - Report any type that has reached the ≥5 threshold since last week close
- If candidates found, present a single confirm gate: "N folders ready to emerge — run
/auditto apply?" (do NOT auto-apply during week-close — just surface the candidates)
Domain Pulse (condensed format):
Weekly Domain Pulse:
- [DomainA]: N pages added this week (X concepts, Y decisions) | Emergence candidate: concepts/ (7 flat)
- [DomainB]: N pages added this week
- [DomainC]: no activity this week
Run /audit to create emerged folders.
Derive activity from git log: git log --since="7 days ago" -- domains/
8. Condensed Audit Snapshot
After the domain pulse, compute the same core metrics as /audit §13 and append a condensed summary to the active weekly note in plan/.
Metrics to compute (use data already gathered this session — do not re-scan):
| Metric | Value |
|---|---|
| Inbox age (oldest unprocessed) | N days |
| Orphan notes | N |
| Broken wikilinks | N |
| Empty brain files | N |
| Stale projects (no activity 30d+) | N |
| Tag violations | N |
Append to the weekly note under a new ## Audit Snapshot heading:
## Audit Snapshot — YYYY-MM-DD
| Metric | Value |
|---|---|
| Inbox age | N days |
| Orphans | N |
| Broken links | N |
| Empty brain files | N |
| Stale projects | N |
| Tag violations | N |
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 · 67 lines · 22 tokens per session scan A 8771ac9312c1
week-close is a command published in the GitHub repository superuser-pal/awesome-second-brain (16 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 607 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
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
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.
capture-tabs
Capture a Chrome research tab group or AI-chat research session into LLM Wiki Inbox markdown, then optionally route it through /inbox or /ingest.