What is pipa-time-tracking?

A time-entry workflow for starting, stopping, switching, reviewing, correcting, or adding past records of work time.

It helps run timers, change the current task, log past time, review summaries, update or archive entries, and check or add tracking credits.

It provides a consistent way to track time without reconstructing activity from screenshots or using unsupported payroll and invoicing features.

pipa-time-tracking — 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-time-tracking

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-time-tracking/github.svg)](https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-time-tracking)

Your own site

<a href="https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-time-tracking"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-time-tracking/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-time-tracking"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-time-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,299 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.00042	$0.03299
Opus 5	$0.00021	$0.01649
Sonnet 5	$0.00008	$0.00660
Haiku 4.5	$0.00004	$0.00330

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

Security

Grade A, and why

pipa-time-tracking 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-time-tracking/SKILL.md · 305 lines

How it starts

The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pipa Time Tracking

User time-tracking req -> Pipa creds -> generic time_tracking/time_entry utility records.

CRITICAL: Use only Toggl-style time entries via generic Pipa agent utility records API. Do not use Clockify, Toggl, screenshots, payroll, invoicing, productivity scoring, passive activity reconstruction, or /v1/time-tracking/* wrapper endpoints.

Keep short todo list: mode, creds, missing question, payload validation, API call, final response.

Workflow

Pick mode. Choose exactly one.
- Start timer: "start tracking this", "start timer for Acme", "track time on frontend fixes" -> start.
- Switch work: "switch to Acme QA" -> switch.
- Stop current timer -> stop.
- Ask what is running -> current.
- Log past time: "log 45 minutes from 9 to 9:45" -> backfill.
- Show entries / summarize time -> review.
- Update/delete/cancel/archive entry -> update/archive.
- Buy credits/top up, check credit balance, or mutating req fails with insufficient_credits -> top-up.
- Payroll, invoicing, screenshots, passive reconstruction, external tracker sync, recurring timers, auto idle detection -> explain V1 unsupported, stop.
If conversation already has successful API response and user asks about that result, answer from known response. Do not call unsupported reporting endpoints.
Load creds. Required before API calls:
- PIPA_API_BASE_URL
- PIPA_API_KEY
- PIPA_EMAIL
- PIPA_USER_TIMEZONE
Aliases:
- PIPA_FOLLOW_UP_API_KEY -> PIPA_API_KEY
- PIPA_FOLLOW_UP_EMAIL -> PIPA_EMAIL
- If canonical and alias values both exist in the same source, canonical wins.
Lookup order:
1. Gateway-injected values.
2. Env vars.
3. Repo-local .pipa/credentials.
4. User-global ~/.pipa/credentials.
Hidden-path rule:
- Do not trust glob/file-search for .pipa/credentials; hidden dirs can be skipped/mishandled.
- Check explicit paths directly: <workspace-root>/.pipa/credentials, then ~/.pipa/credentials.
- Shell helper: resolve root from cwd or git rev-parse --show-toplevel; read Path(root) / ".pipa" / "credentials".
- No files found from glob for .pipa/credentials is inconclusive. Direct-read before asking user for creds.

Read the full file on GitHub · 305 lines

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 · 305 lines · 42 tokens per session scan A 265b9c988fd5

Subscribe to this mod's changes

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

Productivity agent-skills opencode operations pipa

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

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

anti-sleep

Keep a Mac awake with caffeinate during long builds, downloads, or supervised automation runs.

sickn33/agentic-awesome-skills · 22 tokens

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.

Yeachan-Heo/oh-my-claudecode · 41 tokens

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…

jeremylongshore/tons-of-skills-marketplace · 101 tokens

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.

code-yeongyu/oh-my-openagent · 45 tokens