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-daily-shutdowngit 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-daily-shutdown)<a href="https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-daily-shutdown"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-daily-shutdown/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-daily-shutdown"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-daily-shutdown.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.00034 | $0.00555 |
| Opus 5 | $0.00017 | $0.00278 |
| Sonnet 5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
pipa-daily-shutdown 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipa Daily Shutdown
Summarize one workday, close open loops, and prepare tomorrow. Route formal closeout work to its focused operation. Route recurring or scheduled setup to pipa-manage.
Progress
Track this checklist in working notes:
Daily Shutdown Progress
- [ ] Step 1 complete: close today
- [ ] Step 2 complete: compare plan to actual
- [ ] Step 3 complete: resolve open loops
- [ ] Step 4 complete: prepare tomorrow
Workflow
Before step 1, read references/gotchas.md and references/output-contract.md. Use the system date for today. For another date, use the user's request or calendar. Ask one question only if the target day is unclear.
Read ~/.pipa/profile.md and ~/.pipa/CONNECTORS.md when present. Use the profile for goals and preferences. Use mapped tools when present. For unmapped capabilities, use composio-mcp discovery to find tools for ~~project tracker, ~~calendar, and ~~code hosting. Verify live access before reading a source. Use the tracker and calendar as core sources, code hosting for code delivery, and other sources only to resolve a specific outcome or open loop.
- Close today. Gather completed or advanced work, shipped artifacts, decisions, and calendar events. Separate verified completion from movement and unknown outcomes. Relate the day to a known goal; omit the goal check when none is known. A calendar event proves it was scheduled, not attended.
- Compare plan to actual. Use a matching Daily Plan when available. Otherwise, use target-day evidence without showing
baseline unavailable. If the user asks for a comparison, include it in completed, moved, and open work. - Resolve open loops. Give each important unfinished item one disposition: carry forward, delegate, schedule, defer, drop, or
TBD. Add a next action when possible. - Prepare tomorrow. Find the likely first priority, first action, and known calendar constraint. Do not create tasks or events.
What ships with it
4 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.
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 · 36 lines · 34 tokens per session scan A 15bca3f0af2f
pipa-daily-shutdown is a skill published in the GitHub repository lunchpaillola/pipa-skills (3 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 555 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-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.