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 Agentic-Insights/foundry --skill para-pkmgit clone --depth 1 https://github.com/Agentic-Insights/foundryWrote 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/agentic-insights/foundry/para-pkm)<a href="https://agentmods.dev/skills/agentic-insights/foundry/para-pkm"><img src="https://agentmods.dev/badge/skills/agentic-insights/foundry/para-pkm.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.00122 | $0.00992 |
| Opus 5 | $0.00061 | $0.00496 |
| Sonnet 5 | $0.00024 | $0.00198 |
| Haiku 4.5 | $0.00012 | $0.00099 |
Grade A, and why
para-pkm 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 6d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PARA PKM
Organize by actionability, not topic. Projects/Areas/Resources/Archives for optimal AI navigation. Monthly review cadence.
Core Concepts
- Projects = Time-bound goals with deadlines (completes → Archives); includes
projects/stories/for job applications - Areas = Ongoing responsibilities (use
_overview.mdper area for context) - Resources = Reference material; when unsure, put here temporarily
- Archives = Inactive items from any category
Decision Tree
Has deadline/end state? → Projects
Ongoing responsibility? → Areas
Reference material? → Resources (default for uncertain items)
Completed/inactive? → Archives
Quick Start
python scripts/init_para_kb.py <name>- Creates PARA +projects/stories/+ navigation- Identify projects (deadlines) → areas (ongoing) → resources (reference)
python scripts/generate_nav.py- Generate AI navigation
Scripts
| Script | Purpose | Usage |
|---|---|---|
init_para_kb.py |
Scaffold new KB | <name> [--path <dir>] |
validate_para.py |
Check structure, detect anti-patterns | [path] |
archive_project.py |
Archive with metadata (date, origin) | <project-file> [--kb-path] |
generate_nav.py |
Create AI nav (<100 lines) | [--kb-path] [--output] |
Templates
| Template | Purpose |
|---|---|
assets/AGENTS.md.template |
AI navigation index |
assets/project.md.template |
Project file structure |
assets/area-overview.md.template |
Area _overview.md format |
assets/README.md.template |
Knowledge base README |
Patterns by Role
- Developers:
projects/active/features/bugs,areas/professional-development/,resources/coding-standards/ - Consultants:
projects/active/deliverables +projects/stories/,areas/consulting/clients/,resources/templates/ - Researchers:
projects/active/papers/grants,areas/research-program/,resources/literature-review/ - Product Builders:
projects/active/launches,areas/product-development/{active,research,graduated,legacy}/
What ships with it
12 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.
- assets/AGENTS.md.template 636 B
- assets/area-overview.md.template 504 B
- assets/project.md.template 394 B
- assets/README.md.template 1014 B
- references/ai-navigation.md 1.8 KB
- references/common-patterns.md 2.2 KB
- references/decision-guide.md 1.9 KB
- references/para-principles.md 1.8 KB
- scripts/archive_project.py 2.2 KB runs code
- scripts/generate_nav.py 3.2 KB runs code
- scripts/init_para_kb.py 3.4 KB runs code
- scripts/validate_para.py 3.6 KB runs code
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.
- 6d ago First seen · 91 lines · 122 tokens per session scan A 06a8c53efe9a
para-pkm is a skill published in the GitHub repository Agentic-Insights/foundry (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 122 tokens to every session and 992 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-31.
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…
calendar
Manage calendar events via CalDAV (Google/iCloud/Nextcloud) or local ICS files. View, create, and query events.
email-assistant
Read, search, draft, and send emails via Himalaya CLI or Python IMAP/SMTP. Requires email account configuration.