Borrowing it
Nothing to install: this file belongs to AIOSAI/AIPass. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AIOSAI/AIPass/main/.agents/skills/prep/SKILL.mdgit clone --depth 1 https://github.com/AIOSAI/AIPassWrote 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/aiosai/aipass/prep)<a href="https://agentmods.dev/skills/aiosai/aipass/prep"><img src="https://agentmods.dev/badge/skills/aiosai/aipass/prep/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/aiosai/aipass/prep"><img src="https://agentmods.dev/badge/skills/aiosai/aipass/prep.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 Excessive Agency · line 34 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00033 | $0.01496 |
| Opus 5.5 | $0.00013 | $0.00598 |
| Sonnet 5.5 | $0.00007 | $0.00299 |
| Haiku 4.5 | $0.00003 | $0.00150 |
Grade A, and why
prep 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 yesterday.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Wrap-Up
Purpose: Button up everything at the end of a session — or before a /compact. Memories, plans, git — all tidy. Works for both closing out a chat and preparing for compaction.
Workflow: /prep → review output → close chat or /compact
Execution
- Pin the interrupted thread FIRST — before any wrap-up work, write one sentence naming what the conversation was doing when /prep fired (the live task, question, or build mid-flight — "nothing in flight" counts). Prep often auto-triggers mid-task and the wrap-up steps flush the thread from attention; this line is what gets it back. It becomes the Resuming line at the end.
- Read
.trinity/passport.json— re-absorb your identity before writing anything - Do ALL of the following, then confirm what was updated
1. Memories
Each memory file plays a distinct role. Update based on what actually changed this session.
.trinity/passport.json— IDENTITY. Who you are: role, capabilities, principles. Only update if identity genuinely evolved this session..trinity/local.json— YOUR MEMORY. Add/update session entry with a summary of work done. Add key_learnings for anything learned. Update todos[] with current in-flight items — one line each, under 100 chars, no status..trinity/observations.json— YOUR MEMORY OF THE USER. Collaboration insights, preferences, friction points. Skip if nothing new about the user this session.
Entry shape — one rule for all four types
key_learnings, sessions, todos (local.json) and observations (observations.json) all share ONE shape: a list of objects, newest at the top (index 0). Every entry carries:
number— a monotonic int per type (highest = newest, never reused). New entry's number = current max for that type + 1.date— ISO date/datetime.- Plus its text field + extras: key_learnings
{number, date, key, value}· sessions{number, date, summary, status, tags}· todos{number, date, task, priority?}(nostatus— the story lives in sessions and plans) · observations{number, date, note, tags}.
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.
- yesterday Changed · +31 lines 339b64041361
- 1mo ago First seen · 62 lines · 33 tokens per session scan A 9339d06b8f96
prep is a skill published in the GitHub repository AIOSAI/AIPass (306 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,496 once invoked, about $0.0001 per session on Opus 5.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
syncing-memory-filesystem
Diagnose and repair MemFS repository setup, remote sync, authentication failures, optional backup remotes, or merge/rebase conflicts. Do not load for routine memory reads or edits.
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
pre-pr
Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks required tests and docs, then writes Description / Proofs / Fixes.
init
Turn on Rekal memory in the current repository by running rekal init. Use when the user asks to initialize or set up Rekal here, or when a rekal command reported the repository is not initialized. Once per repository. Do not offer this merely because a repo lacks a .rekal/ store — most repos do not want one.
memex-sync
Sync Zettelkasten cards across devices via git.
cartographer-kb-conflict-resolve
Guide an agent through resolving open git rebase conflicts on degraded KB concepts.