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 agentmods add skills/aiosai/aipass/prepnpx skills add AIOSAI/AIPass --skill prepgit 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.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 | $0.00033 | $0.00868 |
| Opus 5 | $0.00016 | $0.00434 |
| Sonnet 5 | $0.00007 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
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 3d 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 — 62 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.
Execution
- Read
.trinity/passport.jsonfirst — re-absorb your identity before writing anything - Do ALL of the following, then confirm what was updated
1. Memories
- .trinity/local.json — Add/update session entry with summary of work done. Add new key_learnings for anything learned this session.
- .trinity/observations.json — Add collaboration insights if anything notable happened. Skip if nothing new.
- .trinity/passport.json — Only update if role/purpose/principles genuinely changed this session.
Entry shape — one rule for all four types: key_learnings, sessions, todos (local.json) and observations (observations.json) are all lists, newest at top (index 0). Every entry carries a number (monotonic int per type — highest = newest, never reused; new = current max + 1) and a date (ISO), plus its text field + extras: key_learnings {number, date, key, value} · sessions {number, date, summary, status, tags} · todos {number, date, task, priority, status} · observations {number, date, note, tags}. Stamp number + date and prepend; don't hand-trim sessions/key_learnings/observations — rollover archives the oldest by number automatically. Todos are the exception — rollover never touches them, so you prune done ones by hand (see Reconcile).
Reconcile todos — verify against reality, don't trust the label. Stored status drifts (a todo finished a past session often never got closed). Audit every open todo against the actual system: file/dir still there? code path in or out? README says what it claims? audit passes? Close what's verifiably done → note it in the session entry, then DELETE the todo from the array (rollover never trims todos — they're operational — so done items left as status: done pile up and go stale across chats), re-scope partials, leave deferred/pending-decision ones open. Fail honestly — remove only on evidence, never to tidy the list. Use ls/find/git ls-files/grep/drone @seedgo audit, not assumptions.
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.
- 3d ago First seen · 62 lines · 33 tokens per session scan A 9339d06b8f96
prep is a skill published in the GitHub repository AIOSAI/AIPass (264 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 868 once invoked, about $0.0002 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
local-tools
Access local system resources including Calendar on macOS and Windows. Use this skill when you need to manage user's schedule directly on their device.
imap-smtp-email
Read and send email via IMAP/SMTP. Check for new/unread messages, fetch content, search mailboxes, mark as read/unread, and send emails with attachments. Works with any IMAP/SMTP server including Gmail, Outlook, 163.com, vip.163.com, 126.com, vip.126.com, 188.com, and vip.188.com.
scheduling-tasks
Schedules reminders and recurring tasks via the letta cron CLI. Use when the user asks to be reminded of something, wants periodic work or check-ins, or needs to list, inspect, replace, or cancel scheduled tasks.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.
e2e
Run end-to-end tests via the CI workflow.