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 kieutrongthien/skills-fullstack --skill plan-progress-reportinggit clone --depth 1 https://github.com/kieutrongthien/skills-fullstackWrote 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/kieutrongthien/skills-fullstack/plan-progress-reporting)<a href="https://agentmods.dev/skills/kieutrongthien/skills-fullstack/plan-progress-reporting"><img src="https://agentmods.dev/badge/skills/kieutrongthien/skills-fullstack/plan-progress-reporting.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.00016 | $0.00595 |
| Opus 5 | $0.00008 | $0.00298 |
| Sonnet 5 | $0.00003 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
plan-progress-reporting 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 7d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Progress Reporting Skill
What it does
- Crafts status updates with outcomes, risks, and next steps.
- Summarizes metrics (velocity, burndown, defect rate) for stakeholders.
- Tailors message per audience (executive, product, engineering).
When to use (khi nào dùng)
- When stakeholders request status or risk assessment.
- Before major milestones/releases to align expectations.
Key operations
- Identify active project; gather metrics from
current-sprint.json, velocity/burndown charts, task logs. - Compile key metrics and narrative: what changed, impact, risks; include RAG with rationale and asks.
- Tailor content length and depth to audience; highlight decisions needed.
- Attach evidence (demo links, PRs, dashboards, burndown/velocity charts); log updates in
memory/YYYY-MM-DD.md.
Output files
projects/<ACTIVE>/reports/status.md— current status, accomplishments, next steps, risks/asks.projects/<ACTIVE>/reports/metrics.csv— velocity, burndown snapshots, defects, lead time (if available).projects/<ACTIVE>/reports/risks.md— risk register with owners and due dates.projects/<ACTIVE>/reports/weekly-report.mdorsprint-review.mdwhen applicable.memory/YYYY-MM-DD.md— log shared updates, risks, and decisions.
Example workflow
- Gather metrics (velocity, burndown, completion %) and qualitative updates from
task-logand sprint files. - Write
status.mdwith RAG, highlights, risks, asks, and links to evidence (demo, PRs, dashboards). - Update
metrics.csvandrisks.md; share with stakeholders; log summary inmemory/YYYY-MM-DD.md.
Best practices (best practice)
- Lead with outcomes and impact; keep metrics brief and relevant.
- Be explicit about risks, mitigations, and help needed.
- Keep updates consistent cadence and format; avoid surprise escalations.
- Use visuals (burndown chart) when possible.
- Keep audience-specific brevity; executives want outcomes/risks/asks; engineering wants detail/links.
- Ensure data sources match AGENTS files (current-sprint.json, velocity/burndown charts) to avoid drift.
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.
- 7d ago First seen · 48 lines · 16 tokens per session scan A 5045d20db381
plan-progress-reporting is a skill published in the GitHub repository kieutrongthien/skills-fullstack (2 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 595 once invoked, about $0.0001 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.