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 getpapi/papi --skill papi-autogit clone --depth 1 https://github.com/getpapi/papiWrote 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/getpapi/papi/papi-auto)<a href="https://agentmods.dev/skills/getpapi/papi/papi-auto"><img src="https://agentmods.dev/badge/skills/getpapi/papi/papi-auto/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/getpapi/papi/papi-auto"><img src="https://agentmods.dev/badge/skills/getpapi/papi/papi-auto.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.00035 | $0.01171 |
| Opus 5.5 | $0.00014 | $0.00468 |
| Sonnet 5.5 | $0.00007 | $0.00234 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
papi-auto 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 today.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
papi-auto
Use papi-plan, papi-build, papi-strategy and papi-idea for the canonical phase rules. This skill coordinates one cycle; it grants no new scope, human review authority, publication, deployment or external messaging.
Modes
dry-run: orient, inspect the current cycle, handoffs and evidence, then show proposed actions. Do not claim tasks, apply plans or edit files.- Resume/default: continue the already approved cycle from its recorded state.
unattended: continue only already authorized work. Never bypass plan approval, human verdicts, access controls or release authority.
Orient and preserve progress
Keep the active project connection and workspace binding fixed. Surface its name
and verify it matches the intended project. Inspect the caller-owned cycle with
build_list; distinguish teammate cycles, claims and person-only decisions.
Use MCP records as project authority, not .papi/ files.
Fetch remote main before new branches. Preserve unrelated dirty work and isolate in a permitted task directory; never auto-stash, reset or discard it. Record the exact base, branch, owner, scope and durable receipts.
- In Progress: inspect its branch, commits, saved changes and owned process before resuming. A status alone is not progress.
- In Review: already built. Read its report and review queue; never rebuild.
- In Cycle/Backlog: check for existing implementation first. Build only eligible approved tasks with a handoff and satisfied prerequisites.
- Done/Cancelled: skip. Never change historical ownership for bookkeeping.
- Already shipped with missing evidence: follow papi-plan's restoration route.
When no cycle is active, prepare at least two coherent eligible tasks, aiming for three when available. Show exact IDs, names, scope and blockers before applying. An approved resume needs no new scope approval. Never silently drop tasks, include another person's work or invent filler. Run a due strategy review in this conversation; material choices require the user's authority. Never force past the planner's gate.
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.
- today First seen · 109 lines · 35 tokens per session scan A fd765ee579b3
papi-auto is a skill published in the GitHub repository getpapi/papi (11 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,171 once invoked, about $0.0001 per session on Opus 5.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-10-16.
Other skills, from other repositories
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
ijfw-ship
Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…