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-strategygit 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-strategy)<a href="https://agentmods.dev/skills/getpapi/papi/papi-strategy"><img src="https://agentmods.dev/badge/skills/getpapi/papi/papi-strategy/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-strategy"><img src="https://agentmods.dev/badge/skills/getpapi/papi/papi-strategy.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.00024 | $0.00416 |
| Opus 5.5 | $0.00010 | $0.00166 |
| Sonnet 5.5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
papi-strategy 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.
What it actually says
papi-strategy
Strategy Reviews
Every 5 cycles, PAPI offers a strategy review — a deep analysis of velocity, estimation accuracy, active decisions, and project direction.
- Don't skip them. They're where compounding value comes from.
- Run in the current conversation. Only verified context pressure warrants a fresh chat; elapsed time, task type and compaction alone do not.
- Reviews produce recommendations that feed into the next plan.
- If the review recommends AD changes, use
strategy_changeto apply them.
Close the review
After apply, verify the stored review and recommendations. Apply authorized decision changes and feed the findings into the next proposed task set. Share externally only when requested, through an available supported tool, with explicit send authorization for the destination. Marketing is not a review gate. Remote HTTP accepts inline output or supported structured chunks; a caller-local output path works only when the connected local workspace server can read it.
Active Decision Lifecycle
Active Decisions (ADs) track architectural and product choices with confidence levels (LOW → MEDIUM → HIGH).
- Check ADs before making architectural choices — run
healthfor the AD summary. - ADs are for product/architecture choices only, not process preferences.
- When new evidence appears, update AD confidence via
strategy_change. - Supersede rather than overwrite — old decisions stay as history.
- An AD conflict is a user decision. Submit it through
ideawithconflicts_with_ad: "AD-N"; preserve its evidence behind the decision gate instead of shelving it. Use the deployment's supported resolution flow. - New ADs should include a
### Reversal Triggersection: specify the signal that would invalidate the stance, the action to take (modify/supersede/abandon), and why writing it now prevents sunk-cost drift later.
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 · 39 lines · 24 tokens per session scan A 880f4e2cf386
papi-strategy is a skill published in the GitHub repository getpapi/papi (11 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 416 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
trace
Resolve a stack trace or error message to the code responsible, using Synapse's code graph. Use when the user pastes a stack trace or asks where an error comes from. Needs Synapse Pro.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.