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 skills/kv0906/pm-kit/progressnpx skills add kv0906/pm-kit --skill progressgit clone --depth 1 https://github.com/kv0906/pm-kitWhat 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.00034 | $0.00517 |
| Opus 5 | $0.00017 | $0.00259 |
| Sonnet 5 | $0.00007 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
progress 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.
What it actually says
/progress — Project Status
Read-only synthesis. Scans vault and outputs status to terminal. Does NOT create files unless --save flag used.
Context
Today's date: !date +%Y-%m-%d
Config: @_core/config.yaml Processing logic: @_core/PROCESSING.md
Input
User input: $ARGUMENTS
Session Task Progress
TaskCreate: "Gather project data"
activeForm: "Scanning vault for project data..."
TaskCreate: "Synthesize report"
activeForm: "Synthesizing status report..."
Processing Steps
-
Parse Input
- Extract project (or "all" for all projects)
- Parse timeframe: --week (default), --since {date}
-
Gather Data
- Scan
daily/*.mdfor project sections in timeframe - Scan
blockers/{project}/*.mdfor open blockers - Scan
docs/{project}/*.mdfor active docs - Scan
decisions/{project}/*.mdfor recent decisions
- Scan
-
Synthesize Report
Output Format
# {Project} Status
**Period**: {start} → {end}
## Shipped
- {item}
## In Progress
- {item}
## Open Blockers
| Blocker | Severity | Owner | Due |
|---------|----------|-------|-----|
| {title} | {sev} | {own} | {d} |
**Critical**: {count} blockers due within 2 days
## Active Docs
- {doc} — {status}
## Recent Decisions
- {decision} — {date}
Note: This command does NOT create any files. Output to terminal only.
Use --save to write to reports/{date}-progress-{project}.md
Export (Optional)
Supports --xlsx, --docx, --pdf, --pptx flags. See .claude/rules/export-formats.md for layout specs and workflow. Complete normal processing first, then generate the formatted file.
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 · 80 lines · 34 tokens per session scan A 421d21db9c6d
progress is a skill published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 517 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 skills, from other repositories
critique-agent
Pressure-test an existing product brief or PRD pack — find gaps, hidden assumptions, inconsistencies, and failure modes before stakeholder review. Use when: critique brief, critique PRD, devils advocate, red team, pressure test, find holes, what could go wrong, stress test the doc, pre-mortem.
interview-frameworks
Frameworks for user interviews, question design, and qualitative research. Use when conducting user interviews, designing interview guides, researching user needs, or gathering qualitative insights. Trigger on: 'create an interview guide', 'how do I interview users', 'customer discovery questions', 'user research…
query-datasets
Answer grounded yes/no questions about what exists in the 03-datasets/ example corpora (supporttickets, calltranscripts) using the local SQLite + FTS5 + vector hybrid index. Use when the user asks 'do/does [corpus] contain/mention/include/have requests for X?', 'any [corpus] about Y?', or similar factual queries over…
critique-prd
Rubric-score a PRD pack (02 + 03) against the 7-dimension PM Brain rubric and run a 4-persona panel review. Returns scores, panel critiques, the single weakest section, a concrete rewrite, and P0/P1 fix lists. Use when: PRD review, score my PRD, rubric review, panel review, rewrite weakest section, critique-prd.
create-prd
Write the PRD pack (02-product-requirements.md + 03-success-metrics.md) on top of an approved product brief. Use when: PRD, product requirements, requirements doc, success metrics, spec writeup, shape the PRD.
create-product-brief
Write concise (2-page) product briefs to get buy-in before investing in full specs. Use when: product brief, one pager, feature brief, quick spec, feature proposal, pitch idea.