agentmods.dev

para-setup

para-setup is a command for coding agents from aroyburman-codes/para-second-brain. It costs 0 tokens per session (607 once invoked), scanned A, original, MIT.

A command that creates a PARA folder system: Projects, Areas, Resources, and Archive. PARA is a way to organize work by whether it is an active project, an ongoing responsibility, useful reference material, or finished work.

In plain words
What is it for?
Use it to choose a root folder, create the four categories, add category instructions, and create starter project and personal-development folders with notes and context files.
Why use it?
It removes the need to design the folder structure and starter files yourself.

Command

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

not rated 2 6mo ago A scan 0 tokens original MIT
View the source file aroyburman-codes/para-second-brain
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-setup
Clone the repo
git clone --depth 1 https://github.com/aroyburman-codes/para-second-brain

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-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/aroyburman-codes/para-second-brain/para-setup.svg)](https://agentmods.dev/commands/aroyburman-codes/para-second-brain/para-setup)
Your own site
<a href="https://agentmods.dev/commands/aroyburman-codes/para-second-brain/para-setup"><img src="https://agentmods.dev/badge/commands/aroyburman-codes/para-second-brain/para-setup.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 607 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 $0.00000 $0.00607
Opus 5 $0.00000 $0.00303
Sonnet 5 $0.00000 $0.00121
Haiku 4.5 $0.00000 $0.00061

Measured 3d ago against content hash 7bdb90f43529, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

para-setup 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 3d 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-setup.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/para-setup

Initialize a PARA (Projects/Areas/Resources/Archive) directory structure on the user's machine.

Usage

/para-setup [path]
  • If [path] is provided, use that as the PARA root directory.
  • If no path is provided, ask the user where they'd like their PARA system. Default suggestion: ~/para/

Steps

  1. Confirm location with the user. Show the default (~/para/) and let them choose.

  2. Create the directory tree using Bash(mkdir -p):

    {PARA_ROOT}/
├── Projects/
├── Areas/
├── Resources/
└── Archive/

  3. Create category READMEs using Write. Pull content from skills/para-system/references/templates.md — use the exact README templates defined there for each category (Projects, Areas, Resources, Archive).

  4. Create 3 starter items with filled-in templates. Pull content from the "Starter Items" section in skills/para-system/references/templates.md:

    Projects/my-first-project/

    • context.md — use the starter project template
    • notes/log.md — use the log template
    • assets/ — empty directory

    Areas/personal-development/

    • context.md — use the starter area template
    • notes/log.md — use the log template
    • assets/ — empty directory

    Resources/useful-references/

    • context.md — use the starter resource template
    • notes/log.md — use the log template
    • assets/ — empty directory

  5. Create .para-config.json at the PARA root. Use the config template from skills/para-system/references/templates.md, replacing {TODAY} with today's date.

  6. Replace all {TODAY} placeholders in every file with today's date in YYYY-MM-DD format.

  7. Show a summary to the user:

    • List the full directory tree created
    • Mention the 3 starter items
    • Point them to the available commands: /para-add, /para-capture, /para-review, /para-status
    • Suggest they start by customizing my-first-project/context.md with a real project

Read the full file on GitHub · 62 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. 3d ago First seen · 62 lines · 0 tokens per session scan A 7bdb90f43529

Subscribe to this mod's changes

para-setup 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 607 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.

Productivityagent-skillsclaude-codeclaude-skillsknowledge-managementparasecond-brain
Related

Other commands, from other repositories

okf

Command "okf" from kimsanguine/llm-brain, covering 인자 파싱, 기본 private export, 🔴 share-ready gate (외부 공유 전 one-way door), legacy step 1: private dry-run 검토 and legacy step 2: private export.

kimsanguine/llm-brain · 14 tokens

query

Command "query" from kimsanguine/llm-brain, covering step 1: index.md 검색, step 2: persisted claim ledger 로드, step 3: wiki 기반 답변 and step 4: 연결 요약 출력.

kimsanguine/llm-brain · 14 tokens

curate

Command "curate" from kimsanguine/llm-brain, covering 인자 파싱, step 1: curate 스크립트 실행, step 2: distill 실행 (--distill 또는 --all 일 때), step 3: reweave 실행 (--reweave 일 때) and step 3.5: 모순 후보 화해 (wiki/contradictionqueue.md 존재 시).

kimsanguine/llm-brain · 22 tokens

doctor

Command "doctor" from kimsanguine/llm-brain, covering 인자, guided 프로필, 실행, 점검 항목 and 결과 해석.

kimsanguine/llm-brain · 20 tokens

ingest

Command "ingest" from kimsanguine/llm-brain, covering 인자 파싱, step 1: 스크립트 실행, url 수집, 파일 추가 and 텍스트 노트.

kimsanguine/llm-brain · 19 tokens

express

Command "express" from kimsanguine/llm-brain, covering 인자 파싱, step 1: express 스크립트 실행, step 2: 콘텐츠 합성 and step 3: 파일 경로 안내.

kimsanguine/llm-brain · 17 tokens