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 agentmods add commands/phuryn/pm-skills/document-appgit clone --depth 1 https://github.com/phuryn/pm-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/commands/phuryn/pm-skills/document-app)<a href="https://agentmods.dev/commands/phuryn/pm-skills/document-app"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/document-app.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.00783 |
| Opus 5 | $0.00022 | $0.00392 |
| Sonnet 5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
document-app 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 4d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/document-app -- Make the System Reviewable
Produce the durable documentation an AI-built app is missing: an honest map of what the system is, who can do what, and where the risk lives. These docs are the foundation every later audit compares the code against.
Invocation
/document-app
/document-app supabase/functions
/document-app the backend
Workflow
Step 1: Scope
Audit $ARGUMENTS. If empty, document the whole repository, prioritizing backend code, auth, data access, background jobs, and anything that sends, schedules, or exposes data.
Step 2: Reverse-Engineer the Docs
Apply the shipping-artifacts skill. Reading the code as the source of truth, produce the applicable documents in documentation/ at the repo root. For large scopes, fan out with parallel subagents — one per core document, each reading the code slice its doc describes — then reconcile the cross-references yourself.
Core (always):
architecture.md— system overview, stack, auth flow, trust boundariesflows.md— the permission-relevant journeys: each protected step's authz check, the trust-boundary crossings, and the side effects each flow causespermissions.md— roles, scope derivation, resource × operation × role matrix, RLS vs. code-enforced checksvariables.md— config & secrets mapped to risk and rotation
Conditional (only if the capability exists — otherwise note its absence in one line):
emails.md— notification path, templates, retry/backoff, failure visibilitycron.md— scheduled-work inventory, idempotency, internal-call authseo.md— SPA preview approach, route coverage, metadata sanitizationautomation.md— embedded agents/automations: trigger, tool surface, steering vs. hard guardrails, output contract, app-owned side effects, approval gates
Be brutally honest about the current state without being paranoid. Skip any conditional document that doesn't apply and say so. Add a "Related Documents" reference in architecture.md for each doc produced. (The test-coverage map, tests.md, is produced separately by /derive-tests.)
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.
- 4d ago First seen · 62 lines · 44 tokens per session scan A f1940d24a4f2
document-app is a command published in the GitHub repository phuryn/pm-skills (25,964 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 783 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-30.
Other commands, from other repositories
buyer-personas
Map the buying committee, then build alternatives-anchored messaging personas.
ideal-customer-profile
Build, enrich, or audit your ICP — trigger events, buyer map, JTBD, disqualifiers.
positioning-messaging
Build or audit positioning statements, messaging, and related output.
gtm-motions
Score and select a GTM motion stack against real deal economics, not a taxonomy tour.
interview-summary
Summarize a customer interview transcript using JTBD analysis.
prioritize
Score and rank initiatives using a GTM-native prioritization framework.