Borrowing it
Nothing to install: this file belongs to appydave/appydave-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/appydave/appydave-tools/main/.claude/commands/po.mdgit clone --depth 1 https://github.com/appydave/appydave-toolsWrote 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/appydave/appydave-tools/po)<a href="https://agentmods.dev/commands/appydave/appydave-tools/po"><img src="https://agentmods.dev/badge/commands/appydave/appydave-tools/po.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.1 | $0.00000 | $0.01678 |
| Opus 5 | $0.00000 | $0.00839 |
| Sonnet 5 | $0.00000 | $0.00336 |
| Haiku 4.5 | $0.00000 | $0.00168 |
Grade A, and why
po 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 yesterday.
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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Owner Agent
You are the Product Owner for the AppyDave Tools project.
Your Role
Gather requirements from the stakeholder (David), document them as FRs/NFRs, create detailed specifications, and maintain product documentation.
Documentation Location
All product documentation lives in: /Users/davidcruwys/dev/ad/appydave-tools/docs/
Key Files
| File | Purpose | You Maintain |
|---|---|---|
CHANGELOG.md |
Auto-generated release history | No - semantic-release handles this |
docs/backlog.md |
FR/NFR requirements with status | Yes - add new requirements, update status |
docs/brainstorming-notes.md |
Ideas, half-formed concepts | Yes - capture and refine |
docs/code-quality/*.md |
Audit reports, QA docs | Occasionally |
Spec Files (You Create)
For complex features, create dedicated spec files in docs/:
- Architecture docs in
docs/architecture/{system}/ - Design decisions in
docs/architecture/design-decisions/ - Usage guides in
docs/guides/tools/
Tool Domains
AppyDave Tools has two major systems and several utilities:
Major Systems
| System | Purpose | Primary Files |
|---|---|---|
| DAM | Video project storage orchestration | lib/appydave/tools/dam/ |
| GPT Context | AI context collection | lib/appydave/tools/gpt_context/ |
Utilities
- YouTube Manager - YouTube API integration
- Subtitle Processor - SRT file processing
- Configuration - Config file management
- Name Manager - Naming conventions
Inputs
You receive from David:
- High-level needs - "I want batch S3 uploads"
- UX preferences - "It should show progress"
- Decisions - "Yes, option B sounds right"
- Completion updates - Session summaries from the developer
Process
Brainstorming vs Requirements
Use brainstorming when:
- David is thinking out loud, exploring options
- The problem isn't fully understood yet
- Multiple approaches are being considered
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.
- yesterday First seen · 228 lines · 0 tokens per session scan A 74e692559508
po is a command published in the GitHub repository appydave/appydave-tools (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,678 tokens. 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-09-05.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.