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 Undertone0809/rudder --skill para-memory-filesgit clone --depth 1 https://github.com/Undertone0809/rudderWrote 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/undertone0809/rudder/para-memory-files)<a href="https://agentmods.dev/skills/undertone0809/rudder/para-memory-files"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/para-memory-files.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00127 | $0.02241 |
| Opus 5 | $0.00063 | $0.01120 |
| Sonnet 5 | $0.00025 | $0.00448 |
| Haiku 4.5 | $0.00013 | $0.00224 |
Grade A, and why
para-memory-files 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PARA Memory Files
Persistent, file-based memory organized by Tiago Forte's PARA method. Three layers: a knowledge graph, daily notes, and tacit knowledge. All paths are relative to $AGENT_HOME.
Three Memory Layers
Layer 1: Knowledge Graph ($AGENT_HOME/life/ -- PARA)
Entity-based storage. Each entity gets a folder with two tiers:
summary.md-- quick context, load first.items.yaml-- atomic facts, load on demand.
$AGENT_HOME/life/
projects/ # Active work with clear goals/deadlines
<name>/
summary.md
items.yaml
areas/ # Ongoing responsibilities, no end date
people/<name>/
companies/<name>/
resources/ # Reference material, topics of interest
<topic>/
archives/ # Inactive items from the other three
index.md
PARA rules:
- Projects -- active work with a goal or deadline. Move to archives when complete.
- Areas -- ongoing (people, companies, responsibilities). No end date.
- Resources -- reference material, topics of interest.
- Archives -- inactive items from any category.
Fact rules:
- Save durable facts immediately to
items.yaml. - Weekly: rewrite
summary.mdfrom active facts. - Never delete facts. Supersede instead (
status: superseded, addsuperseded_by). - When an entity goes inactive, move its folder to
$AGENT_HOME/life/archives/.
When to create an entity:
- Mentioned 3+ times, OR
- Direct relationship to the user (family, coworker, partner, client), OR
- Significant project or company in the user's life.
- Otherwise, note it in daily notes.
For the atomic fact YAML schema and memory decay rules, see references/schemas.md.
Layer 2: Daily Notes ($AGENT_HOME/memory/YYYY-MM-DD.md)
Raw timeline of events -- the "when" layer.
- Write continuously during conversations and agent work when a memory-worthy signal appears.
- Extract durable facts to Layer 1 during heartbeats.
- Treat daily notes as the first capture layer, not the final destination for stable preferences, entity facts, or shared project knowledge.
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.
- 8d ago First seen · 219 lines · 127 tokens per session scan A 7905abe53f55
para-memory-files is a skill published in the GitHub repository Undertone0809/rudder (288 stars, last pushed today), licensed Apache-2.0. It adds 127 tokens to every session and 2,241 once invoked, about $0.0006 per session on Opus 5. 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-30.
Other skills, from other repositories
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
Migrate
Intakes external content, classifies chunks against LifeOS taxonomy, commits with provenance. Sources: .md/.txt, stdin, LifeOS dirs, CLAUDE.md/Cursor/OpenAI Custom Instructions, Obsidian/Notion/Apple Notes exports. MigrateScan classifies → routing table. MigrateApprove with…
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…
email-assistant
Read, search, draft, and send emails via Himalaya CLI or Python IMAP/SMTP. Requires email account configuration.
calendar
Manage calendar events via CalDAV (Google/iCloud/Nextcloud) or local ICS files. View, create, and query events.