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.
git clone --depth 1 https://github.com/aroyburman-codes/para-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/aroyburman-codes/para-second-brain/para-review)<a href="https://agentmods.dev/commands/aroyburman-codes/para-second-brain/para-review"><img src="https://agentmods.dev/badge/commands/aroyburman-codes/para-second-brain/para-review.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.1 | $0.00000 | $0.00730 |
| Opus 5 | $0.00000 | $0.00365 |
| Sonnet 5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
para-review 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/para-review
Walk through your PARA system to update statuses, archive completed items, and capture new ones.
Usage
/para-review [weekly|monthly]
weekly(default): Quick 10-15 minute review of active itemsmonthly: Deeper review including strategic alignment and resource refresh
Steps
Find the PARA Root
Look for .para-config.json in:
- Current working directory
~/para/- Walk up from current directory
If not found, tell the user to run /para-setup first.
Weekly Review
Walk through each section interactively:
1. Projects Scan
- List all items in
Projects/(exclude Archive) - For each project, read
context.mdand show: name, current phase, health, target date - Ask the user for each: "Still accurate? Update needed? Ready to archive?"
- If the user wants to update, edit the
context.mdstatus fields - If ready to archive, move the folder to
Archive/usingBash(mv)
2. Areas Check
- List all items in
Areas/ - For each area, read
context.mdand show: name, health status - Ask: "Standards being maintained? Needs attention?"
- Update health status if needed
3. Resources Quick Scan
- List all items in
Resources/ - Show name and last reviewed date from
context.md - Flag any not reviewed in 3+ months
- Ask if any should be archived
4. Capture Round
- Ask: "Anything new to capture? New projects, areas, or resources?"
- If yes, use the para-add workflow to create new items
5. Summary
- Show a recap: items reviewed, items updated, items archived, items added
- Add a log entry to each reviewed item's
notes/log.md:- Weekly review: [status]
Monthly Review (adds to weekly)
Do everything in the weekly review, plus:
6. Strategic Alignment
- Show all active projects and ask: "Are these still aligned with your goals?"
- Ask: "Any projects that should be killed or paused?"
- Ask: "Any new projects emerging from your areas or resources?"
7. Resource Deep Refresh
- For each resource, show the full summary and key takeaways
- Ask: "Still relevant? Needs updating? Archive?"
- Update the "Last Reviewed" field to today's date for reviewed resources
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 First seen · 86 lines · 0 tokens per session scan A f096496463af
para-review is a command published in the GitHub repository aroyburman-codes/para-second-brain (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 730 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-31.
Other commands, from other repositories
daily-okr
Run a daily knowledge compound loop (7 KR). Invoke with /daily-okr or "start my daily review".
replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
firm
Convene your standing AI staff — memos on every beat, a board session without you, minutes with dissent preserved.
ship-a-feature
Workflow recipe — take a feature idea from fuzzy brief to launch plan by chaining 5 skills.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
rescue-an-account
Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.