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 lunchpaillola/pipa-skills --skill pipa-follow-up-remindersgit clone --depth 1 https://github.com/lunchpaillola/pipa-skillsWrote 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/lunchpaillola/pipa-skills/pipa-follow-up-reminders)<a href="https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-follow-up-reminders"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-follow-up-reminders/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/lunchpaillola/pipa-skills/pipa-follow-up-reminders"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-follow-up-reminders.svg" alt="Reviewed on agentmods" width="80" 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.03014 |
| Opus 5 | $0.00061 | $0.01507 |
| Sonnet 5 | $0.00024 | $0.00603 |
| Haiku 4.5 | $0.00012 | $0.00301 |
Grade A, and why
pipa-follow-up-reminders 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 12d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipa Follow-Up Reminders
User reminder request -> verified email + resolved time -> Pipa one-shot email reminder.
CRITICAL: Create or cancel only deterministic one-shot email reminders through https://pailflow-chat-gateway.fly.dev. Reminders can only go to the verified email attached to the API key. Do not invent list, read, update, pause, resume, recurring reminder, inbox-watch, reply-detect, SMS, Slack, Gmail scheduled-send, or arbitrary-recipient flows.
Keep a short todo list while executing this skill so context stays clean: mode, credentials, missing question if any, payload validation, API call, final response.
Workflow
-
Pick mode.
Choose exactly one mode.
- User asks for a future email reminder, such as “email me tomorrow,” “remind me by email,” or “follow up with me in two hours” -> create mode. Continue step 2.
- User asks to cancel a scheduled Pipa Follow-Up reminder -> cancel mode. Continue step 2.
- User asks to buy credits, top up, or a create request fails with
insufficient_credits-> top-up mode. Continue step 2. - User asks for reminder listing, updates, recurring reminders, inbox monitoring, reply detection, Gmail scheduled send, SMS, Slack, or reminders to another person -> explain V1 does not support that flow, then stop.
Skip ahead: If the conversation already contains a successful API response and the user asks about that result, answer from the known response. Do not call unsupported read/list APIs.
-
Load credentials.
Load these values before API calls. Distinguish durable user credentials from hosted-run credentials:
PIPA_FOLLOW_UP_API_KEYPIPA_FOLLOW_UP_EMAILPIPA_USER_TIMEZONE
Lookup order:
- Gateway-injected values.
- Environment variables.
- Repo-local
.pipa/credentials. - User-global
~/.pipa/credentials.
Credential rules:
pipa_agent_v1.*keys are hosted-run credentials, not durable user keys.- They can expire. If one fails, say the hosted-run credential expired, not the user's reminder credential.
- Do not write
pipa_agent_v1.*keys into user-managed credential files yourself. - If a user-managed credentials file contains an expired
pipa_agent_v1.*key, ignore/remove that key and continue lookup before starting email-code setup. - Email-code verification returns durable user keys. Those are the keys to store for local/persistent skill use.
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.
- 12d ago First seen · 227 lines · 122 tokens per session scan A 732cf4268e59
pipa-follow-up-reminders is a skill published in the GitHub repository lunchpaillola/pipa-skills (3 stars, last pushed 3d ago), licensed MIT. It adds 122 tokens to every session and 3,014 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
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
anti-sleep
Keep a Mac awake with caffeinate during long builds, downloads, or supervised automation runs.
minimal-code-discipline
YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away.
workflow
Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use…
give-me-tips
Explains any senpi tip in depth, including Tip: lines in the TUI. Use when the user asks about a tip, what a tipped feature does, or which tips they can see.