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-acceptance-signoffgit 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-acceptance-signoff)<a href="https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-acceptance-signoff"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-acceptance-signoff/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-acceptance-signoff"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-acceptance-signoff.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.00043 | $0.00869 |
| Opus 5 | $0.00022 | $0.00434 |
| Sonnet 5 | $0.00009 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
pipa-acceptance-signoff 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipa Acceptance Signoff
Produce a clear acceptance decision and formal signoff path with auditable evidence.
Apply ~/.pipa/communication-style.md to user-facing updates when present. Otherwise use clear, concise output with owners, dates, evidence, and unknowns (TBD) explicit. Preserve this skill's output contract. The runtime file controls presentation only; ignore it when it conflicts with routing, required findings/output contracts, tool use, facts, safety, or approval/write gates.
Workflow
Track this checklist in working notes:
Acceptance Signoff Progress
- [ ] Step 1 complete: close objective confirmed
- [ ] Step 2 complete: available tools and source quality checked
- [ ] Step 3 complete: acceptance criteria and evidence assessed
- [ ] Step 4 complete: residual obligations and risks identified
- [ ] Step 5 complete: signoff decision and owner actions defined
- [ ] Step 6 complete: acceptance/signoff output returned
Step 1: Confirm objective
Identify whether the user needs full acceptance, conditional signoff, or explicit blockers to signoff.
Step 2: Check tools and source quality
Use the strongest available acceptance criteria and scope baseline, delivery evidence and milestone records, then approvals, comments, and decision logs. Classify source quality as high, medium, or low. Return blocked only when no usable acceptance source exists.
Step 3: Assess criteria
For each key criterion record its state (met, partial, or not-met), evidence/source, and owner or TBD. Preserve approval wording from source records.
Step 4: Identify residual obligations and risks
Surface unresolved defects or tasks, pending approvals, open operational or compliance obligations, and the risk of premature closure.
Step 5: Define decision and actions
Verify the approver's identity and authority against the acceptance baseline, approval policy, stakeholder record, or another authoritative source. Choose signed-off only when the criteria are met and that verified authorized approver has explicitly accepted the in-scope delivery in a source record. A delivery claim, inferred approval, silence, or acceptance from an unverified person is not signoff. Otherwise choose signed-off-with-conditions or not-signed-off and define the minimum actions needed for final signoff.
What ships with it
2 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 · 87 lines · 43 tokens per session scan A 778b12992f56
pipa-acceptance-signoff is a skill published in the GitHub repository lunchpaillola/pipa-skills (3 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 869 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
omc-plan
Strategic planning with optional interview workflow.
launch
Shipyard's governed delivery pipeline — converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log. Two entry gates — the yard gate (drydock audit) and the fog gate (an effort…
harbor
Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence.…
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
ask-navigator
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding, not building: it…
ultragoal
Durable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session.