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 the-metafactory/soma --skill migrate-pai-purposegit clone --depth 1 https://github.com/the-metafactory/somaWrote 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/the-metafactory/soma/migrate-pai-purpose)<a href="https://agentmods.dev/skills/the-metafactory/soma/migrate-pai-purpose"><img src="https://agentmods.dev/badge/skills/the-metafactory/soma/migrate-pai-purpose/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/the-metafactory/soma/migrate-pai-purpose"><img src="https://agentmods.dev/badge/skills/the-metafactory/soma/migrate-pai-purpose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 67 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00113 | $0.02470 |
| Opus 5 | $0.00056 | $0.01235 |
| Sonnet 5 | $0.00023 | $0.00494 |
| Haiku 4.5 | $0.00011 | $0.00247 |
Grade A, and why
migrate-pai-purpose 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 9d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate PAI's life-OS into Soma Purpose + memory
soma migrate pai moves identity + memory + a mechanical purpose.md. It does not decide where the rest of PAI's imported life-OS belongs, and its identity phase overwrites purpose.md with a raw concatenation each run. This skill finishes the job: it keeps the Purpose compartment lean and curated, and routes the imported breadth into Soma memory where recall can surface it — without bloating the Purpose that ships in every prompt.
Terminology: Soma's compartment is Purpose; the PAI life-OS term for it is killed in Soma (
Purposeis the only word). Below, the PAI source directoryprofile/imports/claude/TELOS/and its filenames are referenced only as the literal imported artifacts they are.
Core principle
Soma's Purpose is four portable fields — Mission / Goals / Principles / Commitments — the durable "why" projected into every session. PAI's imported life-OS is a ~19-category tree. They are not the same size and must not be conflated:
- Purpose-grade content → distilled into the four Purpose fields (a few lines each).
- Context-grade content (mental models, frames, challenges, lessons, narratives) → Soma memory notes, surfaced on demand by recall.
- Time-bound content (status, projects) → work-state / algorithm-runs, never Purpose.
Never dump whole imported files into purpose.md. The full snapshots already live under profile/imports/claude/; memory notes carry a distillation plus a --source-of-truth pointer back to the snapshot.
Disposition table
Source files live under profile/imports/claude/TELOS/:
| Imported file | Goes to | As |
|---|---|---|
MISSION.md (M#) |
Purpose → Mission (1–2 sentences) + Goals (the durable M0–Mn) | curated purpose.md |
BELIEFS.md (B#) |
Purpose → Principles (the load-bearing few) and a memory note (full B-set) | both |
STRATEGIES.md (S#) + master-narrative filter |
Purpose → Commitments (the decision filters) | curated purpose.md |
MODELS.md (MO#) |
memory note | semantic |
FRAMES.md (FR#) |
memory note | semantic |
CHALLENGES.md (C#) |
memory note | semantic |
LEARNED.md |
memory note | semantic |
NARRATIVES.md, WISDOM.md, PROBLEMS.md, IDEAS.md, TRAUMAS.md, WRONG.md, PREDICTIONS.md, BOOKS.md, MOVIES.md |
memory note iff non-empty (see step 2) | semantic / reference |
STATUS.md, PROJECTS.md |
work-state, not Purpose or durable memory | leave in archive |
GOALS.md (G#) |
only durable goals → Purpose.Goals; project/time-bound rows → work-state | curated purpose.md |
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.
- 9d ago First seen · 107 lines · 113 tokens per session scan A aa4b8531dd20
migrate-pai-purpose is a skill published in the GitHub repository the-metafactory/soma (8 stars, last pushed 4d ago), licensed MIT. It adds 113 tokens to every session and 2,470 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.