para-capture

para-capture is a command for Claude Code from aroyburman-codes/para-second-brain. It costs 0 tokens per session (510 once invoked), scanned A, original, MIT.

A quick-capture command for adding a note from the current conversation to a PARA item. PARA organizes information as Projects, Areas, Resources, and Archive.

In plain words
What is it for?
Use it to save a supplied note, or a summary of the current topic, to the log of a selected active project, area, or resource.
Why use it?
Useful decisions and observations can get lost when they are not recorded immediately. This helps place a note in the relevant item's log without interrupting the work.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the para-second-brain plugin — 1 skill, 5 commands shipped together

Install

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.

agentmods
npx agentmods add commands/aroyburman-codes/para-second-brain/para-capture
Clone the repo
git clone --depth 1 https://github.com/aroyburman-codes/para-second-brain

Made for: Claude Code.

Or install para-second-brain, the plugin that ships this one along with the rest of its 1 skill, 5 commands.

Wrote 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.

agentmods badge for para-capture

README.md
[![agentmods](https://agentmods.dev/badge/commands/aroyburman-codes/para-second-brain/para-capture.svg)](https://agentmods.dev/commands/aroyburman-codes/para-second-brain/para-capture)
Your own site
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 510 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 5d ago against content hash 00f03aeb4e62, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

commands/para-capture.md · 67 lines

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

  1. 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.

  2. Determine the text to capture. Use the provided text, or ask the user / summarize the conversation.

  3. 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.md in Projects/, Areas/, and Resources/.

  4. 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.

  5. Read the existing log first to check for today's date header and to append correctly.

  6. 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 Read to check existing log content before writing.
  • Use Edit to append to existing files (preferred) or Write if 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 in YYYY-MM-DD format.

Read the full file on GitHub · 67 lines

Changes

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.

  1. 5d ago First seen · 67 lines · 0 tokens per session scan A 00f03aeb4e62

Subscribe to this mod's changes

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.