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/aroyburman-codes/para-second-brain/para-capturegit 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-capture)<a href="https://agentmods.dev/commands/aroyburman-codes/para-second-brain/para-capture"><img src="https://agentmods.dev/badge/commands/aroyburman-codes/para-second-brain/para-capture.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.00510 |
| Opus 5 | $0.00000 | $0.00255 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
para-capture 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.
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.
/para-capture
Quick-capture a note from the current conversation into a PARA item's log.
Usage
/para-capture [text]
/para-capture
- If
[text]is provided, capture that text directly. - If no text is provided, ask the user what they want to capture — or summarize the current conversation topic and offer to capture that.
Examples:
/para-capture "Decided to use React for the frontend"
/para-capture Key insight from today's meeting: prioritize mobile first
/para-capture
Steps
-
Find the PARA root. Look for
.para-config.jsonin:- Current working directory
~/para/- Walk up from current directory
If not found, tell the user to run
/para-setupfirst. -
Determine the text to capture. Use the provided text, or ask the user / summarize the conversation.
-
Find the right item. Either:
- Ask the user which item to capture to
- If the context makes it obvious (e.g., they're working on a specific project), suggest the most likely item
- List active items and let them pick
To list items, scan for directories containing
context.mdin Projects/, Areas/, and Resources/. -
Append to the item's
notes/log.md. Use this format:## {TODAY} - {captured text}If today's date header already exists in the log, append the bullet under the existing header instead of creating a duplicate date.
-
Read the existing log first to check for today's date header and to append correctly.
-
Show confirmation with:
- What was captured
- Where it was saved (full path)
- The item name
If PARA Item Doesn't Have notes/log.md
Create it using the Log Template from skills/para-system/references/templates.md, then append the capture.
Important
- Use
Readto check existing log content before writing. - Use
Editto append to existing files (preferred) orWriteif creating new. - Always preserve existing log entries — never overwrite.
- Keep captured text concise. If the user provides a long block of text, offer to summarize it.
- Replace
{TODAY}with today's date inYYYY-MM-DDformat.
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 · 67 lines · 0 tokens per session scan A 00f03aeb4e62
para-capture 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 510 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.