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 avizmarlon/agent-skills --skill progress-md-businessgit clone --depth 1 https://github.com/avizmarlon/agent-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/skills/avizmarlon/agent-skills/progress-md-business)<a href="https://agentmods.dev/skills/avizmarlon/agent-skills/progress-md-business"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/progress-md-business/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/avizmarlon/agent-skills/progress-md-business"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/progress-md-business.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.00050 | $0.02292 |
| Opus 5 | $0.00025 | $0.01146 |
| Sonnet 5 | $0.00010 | $0.00458 |
| Haiku 4.5 | $0.00005 | $0.00229 |
Grade A, and why
progress-md-business 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 11d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROGRESS.md — Executive Dashboard for Business Projects
This skill enforces the creation and maintenance of PROGRESS.md as the authoritative executive dashboard for any business or product project. The file is read first by stakeholders and AI agents to understand current state, next phase, and key metrics.
Core Rule
Every business or product project MUST have PROGRESS.md at the repository root. This file serves as the single source of truth for project phase, vision, milestones, and impact metrics. It is NOT a changelog, NOT a technical design document, and NOT a session handoff—it is the executive view.
What PROGRESS.md Contains
- Project phase — current state (Validation → Build → Launch → Growth → Paused → Cancelled)
- Project vision — problem statement, target customer, differentiated value, revenue model
- High-level milestones — key deliverables by phase with completion status
- Impact metrics — quantitative measures of progress (user growth, retention, revenue, engagement, etc.)
- Current blockers — what is preventing progress, with severity
- Next phase transition criteria — what must be true to move to the next phase
What PROGRESS.md Does NOT Contain
- Technical changelog → lives in
CHANGELOG.md(structured, versioned) - Architecture decisions → live in
ADRsorarchitecture-decisions.md - Inter-session context → lives in
session-handoff.mdor equivalent - Code review state → lives in
review-state.mdor inline pull requests - Implementation details → live in issue trackers, code comments, design docs
PROGRESS.md is executive summary only. It points to other documents rather than duplicating them.
Template Structure
Use this structure as a starting point. Customize sections based on project type (B2B SaaS, consumer app, marketplace, etc.):
# PROJECT_NAME — PROGRESS
## Current Phase
🔵 **Build** — ETA next phase: [DATE]
## Vision
**Problem:** [one-sentence problem statement]
**ICP:** [ideal customer profile]
**USP:** [unique value vs. alternatives]
**Revenue Model:** [how money flows]
## Milestones (Current Phase: Build)
- [✓ / ○] Milestone A — [target date]
- [✓ / ○] Milestone B — [target date]
- [✓ / ○] Milestone C — [target date]
## Key Metrics (Last Updated: [DATE])
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| [Metric A] | [current] | [goal] | [trend: ↑ / ↓ / → ] |
| [Metric B] | [current] | [goal] | [trend] |
## Blockers
🔴 **[Blocker Title]** — [description, impact]
🟡 **[Blocker Title]** — [description, impact]
## Next Phase Criteria
To transition to [Next Phase], these conditions must be met:
- Condition 1
- Condition 2
- Condition 3
## Session Updates
- **[DATE]** — [what changed; link to session handoff or PR if applicable]
- **[DATE]** — [what changed]
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.
- 11d ago First seen · 201 lines · 50 tokens per session scan A 98fdd0f03181
progress-md-business is a skill published in the GitHub repository avizmarlon/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 2,292 once invoked, about $0.0003 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-31.
Other skills, from other repositories
design-inventory
Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse mapping; token…
prd-creator
This skill helps PMs draft lightweight PRDs. It should be used when a PM wants to define a new feature, brainstorm requirements, or prep for sprint planning. Triggers include "I have a feature idea", "help me write a PRD", "let's break this into stories", or "what do I need for sprint planning". Optimized for speed …
upload-artifact
Upload a file as a ClosedLoop document (PRD, implementation plan, feature, or template). Reads file content and uploads via MCP without consuming conversation context. Also supports creating new versions of existing documents. Triggers on: "upload artifact", "upload PRD", "upload implementation plan", "upload…
workspace-builder
Build ServiceNow App Engine Studio applications — sysscope creation, scoped tables, sysawworkspace with lists/forms, the sysux record chain behind UI Builder workspaces, data brokers, and application export readiness checks. Never create a UI Builder page by inserting a sysuxpage row.
problem-management
Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.
cross-repo-cache
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…