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 skills add aroyburman-codes/para-second-brain --skill para-systemgit 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/skills/aroyburman-codes/para-second-brain/para-system)<a href="https://agentmods.dev/skills/aroyburman-codes/para-second-brain/para-system"><img src="https://agentmods.dev/badge/skills/aroyburman-codes/para-second-brain/para-system/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/skills/aroyburman-codes/para-second-brain/para-system"><img src="https://agentmods.dev/badge/skills/aroyburman-codes/para-second-brain/para-system.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.00000 | $0.00505 |
| Opus 5.5 | $0.00000 | $0.00202 |
| Sonnet 5.5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
para-system 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 1mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PARA Second Brain System
You have access to the PARA (Projects/Areas/Resources/Archive) methodology for organizing work and knowledge.
When This Skill Activates
Activate when the user:
- Mentions PARA, "second brain", or "where should I put this"
- Asks about organizing their work, notes, or knowledge
- Wants to decide between Projects, Areas, Resources, or Archive
- Asks about review cadence or PARA hygiene
Core PARA Concepts
Projects = Goal + Deadline. Bounded efforts with a clear finish line. Areas = Ongoing Responsibility. No end date — standards to maintain. Resources = Reference Material. Things to find later, no action required now. Archive = Inactive Items. Done, paused, or deprecated — not deleted, just shelved.
Quick Decision Tree
Has a clear end goal + deadline? → Projects
Ongoing responsibility to maintain? → Areas
Reference material for later? → Resources
Done or no longer relevant? → Archive
None of the above? → Don't capture it.
Key Rules
- 8-10 active projects max. More means you're spread too thin.
- Archive aggressively. Clutter has real cognitive cost. Archiving is free.
- Capture fast, organize later. Don't agonize over categories — the weekly review is when you sort things out.
- Every item needs a filled-in context.md. Empty templates are noise.
- Cross-reference related items. Projects often connect to Areas and Resources.
Available Commands
/para-setup [path]— Initialize a PARA directory structure/para-add <category> <name>— Add a new item to any category/para-review [weekly|monthly]— Walk through your system and update statuses/para-capture [text]— Quick-capture a note from the current conversation/para-status [category]— See an overview of your PARA system
Review Cadence
- Weekly (30 min): Scan projects, check areas, capture and archive
- Monthly (60 min): Weekly + strategic alignment + resource refresh
- Quarterly (90 min): Monthly + growth review + system health check
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 56 lines · 0 tokens per session scan A 2d64eb72a845
para-system is a skill published in the GitHub repository aroyburman-codes/para-second-brain (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 505 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 skills, from other repositories
apply
A browser-based job application workflow for submitting applications through services such as Ashby, Greenhouse, Lever, and Hacker News. It uses prepared candidate information, answers, job links, and cover letters.
behavior-design
Use when a goal must be converted into a repeatable behavior, cue, SOP, review cadence, and identity-aligned reinforcement.
daily-okr
Use when planning or closing a daily knowledge-compounding cycle across input, cognition, wiki, behavior, creativity, output, and feedback.
screenpipe-api
Query the user's local and synced-device data via the screenpipe REST API at localhost:3030 — recordings, audio, UI, meetings, connected services, and memory. Use for screen activity, other-device or cross-device history, productivity, media export, connections, durable memory, or discovering and automating saved…
retro-lost
Run a retrospective for an abandoned agent session (untouched for over 24 hours, never closed with a retro): rebuild context cold from the transcript, list what was built, sort Keep/Drop/Try and file the durable parts. Use from a nightly routine or on demand. Triggers: /retro-lost, retro for an abandoned session.
nsr
A routine for starting a new, visible coding-agent session automatically through a scheduled task, so it appears in the recent-session list without someone pressing a start button.