What is pipa-daily-plan?

A workflow for choosing and organizing the work someone can complete during one workday.

Use it to create a daily plan, choose the most useful next task, and identify an action that can unblock delayed work.

It brings together due work, priorities, dependencies, meetings, and goals so the day has a practical focus.

pipa-daily-plan — Skill for Claude Code and Codex by lunchpaillola

Install

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.

Any agent

npx skills add lunchpaillola/pipa-skills --skill pipa-daily-plan

Clone the repo

git clone --depth 1 https://github.com/lunchpaillola/pipa-skills

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-daily-plan/github.svg)](https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-daily-plan)

Your own site

<a href="https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-daily-plan"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-daily-plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-daily-plan"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-daily-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 431 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00031	$0.00431
Opus 5	$0.00015	$0.00216
Sonnet 5	$0.00006	$0.00086
Haiku 4.5	$0.00003	$0.00043

Measured 12d ago against content hash 118d4fb0d745, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

pipa-daily-plan 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.

skills/pipa-daily-plan/SKILL.md · 24 lines

What it actually says

Pipa Daily Plan

Create a brief for one workday. Route recurring or scheduled setup to pipa-manage.

Follow this workflow. Keep a todo list to track each step.

Workflow

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 ~~project tracker and ~~calendar as core sources. Use ~~code hosting for code delivery. Use prior briefs, chat, email, or a knowledge base only to answer a specific planning question.
Gather due work, current or active work, priorities, dependencies, calendar commitments, and stated goals or profile preferences.
Find work the user can advance today. If due work is blocked, select an unblock step. If none exists, flag the block and continue to executable work.
Choose the main focus in this order: overdue or due-today work, current or active work, then the best ticket that supports the user's goals or preferences. Do not estimate task size or forecast capacity.
Write the read-only brief with references/output-contract.md. Show each exact external write and require separate approval before execution; report its result. End with a short sources line that names only the apps and material records used.

Files

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.

Changes

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 · 24 lines · 31 tokens per session scan A 118d4fb0d745

Subscribe to this mod's changes

pipa-daily-plan is a skill published in the GitHub repository lunchpaillola/pipa-skills (3 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 431 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.

Planning agent-skills opencode operations pipa

autoresearch

Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill…

lunchpaillola/lola-opencode · 100 tokens

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.

lunchpaillola/lola-opencode · 63 tokens

json-canvas

Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

lunchpaillola/lola-opencode · 54 tokens

obsidian-markdown

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

lunchpaillola/lola-opencode · 71 tokens

compound

Capture and compound learnings from conversations into reusable commands and skills through interactive dialogue.

lunchpaillola/lola-opencode · 17 tokens

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…

lunchpaillola/lola-opencode · 102 tokens