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 deployment-completeness-auditgit 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/deployment-completeness-audit)<a href="https://agentmods.dev/skills/getpapi/papi/deployment-completeness-audit"><img src="https://agentmods.dev/badge/skills/getpapi/papi/deployment-completeness-audit/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/deployment-completeness-audit"><img src="https://agentmods.dev/badge/skills/getpapi/papi/deployment-completeness-audit.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.00044 | $0.00686 |
| Opus 5.5 | $0.00018 | $0.00274 |
| Sonnet 5.5 | $0.00009 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
deployment-completeness-audit 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit deployment completeness
Read the owning project's source, release policy and current evidence before making claims. This skill diagnoses; it grants no deployment, infrastructure access, production SQL, publication or task-creation authority. Use available authenticated read-only surfaces. A missing credential or environment receipt is unverified, not a proved deployment defect.
Trace the production path
- Database operations and migrations. Locate the project's actual migration directory and migration ledger. Trace calls to stored operations and their fallback conditions. Compare the expected signature/schema with deployed evidence when accessible. A disposable-database replay proves source compatibility, not production activation. Do not assume Supabase or a cloud management API.
- Configuration. Trace each changed environment/configuration name from its owning source to the documented release setting. Record names only; never print secret values. Check default behavior, unset values, feature flags and per-environment activation.
- Routes, jobs and entry points. Follow changed UI actions, endpoints, scheduled jobs and queue handlers from registration to execution. A file existing does not mean a route or scheduler reaches it. Inspect the actual canonical runtime and routing, without creating another helper service.
- Dependencies and artifacts. Check imports, pinned runtime compatibility, artifact digest and the release's actual installed version. Reuse existing exact-source receipts. Compilation and successful tests prove their named scope; they do not prove activation.
- Schema and types. Compare owning database definitions with domain types and selected query projections. Verify caller/tenant predicates before pagination and actual serialization shapes. Never infer a global dataset from RLS alone.
- Multiple adapters and surfaces. Locate the project's actual adapter interface and supported implementations. Trace equivalent methods and their authentication/transaction guarantees. Check whether a stub is supported architecture, obsolete compatibility or an unimplemented production path. A comment is a hypothesis to verify, not permanent proof that a fallback is correct.
- Delivery. Trace exact reviewed source through qualification, immutable artifact, authorized installation, health and the changed user flow. Read the actual remote commit/tag and installed runtime receipt. Keep human acceptance distinct from an agent audit.
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 · 29 lines · 44 tokens per session scan A 6aee39d88877
deployment-completeness-audit is a skill published in the GitHub repository getpapi/papi (11 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 686 once invoked, about $0.0002 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-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
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-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.