What is report-daily-progress?

A daily project-progress report generator that creates a self-contained HTML page. It combines backlog status, a burndown chart, sprint scope, and that day’s code merges; a burndown chart compares planned remaining work with actual remaining work over time.

Use it to create the day’s report with sprint details, item status, point totals, repository activity, scope changes, and progress charts.

It gives a team one stand-up view of delivery progress, remaining work, and recent development activity.

report-daily-progress — Skill for Claude Code by atman-33/workhub

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add atman-33/workhub

Claude Code

/plugin install team-ops

Made for: Claude Code.

Or install team-ops, the plugin that ships this one along with the rest of its 13 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/atman-33/workhub/report-daily-progress/github.svg)](https://agentmods.dev/skills/atman-33/workhub/report-daily-progress)

Your own site

<a href="https://agentmods.dev/skills/atman-33/workhub/report-daily-progress"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/report-daily-progress/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/atman-33/workhub/report-daily-progress"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/report-daily-progress.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 499 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00062	$0.00499
Opus 5.5	$0.00025	$0.00200
Sonnet 5.5	$0.00012	$0.00100
Haiku 4.5	$0.00006	$0.00050

Measured 1mo ago against content hash 4f8602f657a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

report-daily-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 1mo 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.

plugins/team-ops/skills/report-daily-progress/SKILL.md · 39 lines

What it actually says

Daily progress report

Produce projects/<p>/reports/daily/<date>.html — the page the team opens at stand-up.

Steps

Ensure fresh data (token-free; run unless already run today):

node "${CLAUDE_PLUGIN_ROOT}/scripts/sync/sync-project-repos.mjs" <project>
node "${CLAUDE_PLUGIN_ROOT}/scripts/snapshot/progress-snapshot.mjs" <project>

Read the inputs: backlog/progress-history.jsonl (all lines for the current sprint), backlog/items/* frontmatter, the current sprint's scope.json + planning.md (for scope-change notes), and each repo's pbi-activity.json + commits.jsonl tail (today's commits).
Write one self-contained HTML file (inline CSS/SVG, no external assets; text in the team content language):
- Header: project, date, sprint id + goal, days remaining.
- Burndown (inline SVG): ideal line from scope.json total points → 0 over the sprint dates vs actual sprintRemainingPoints per day from the history; annotate scope changes.
- Status board: table of sprint items — id (linked to the item file), title, status, points, assignee, and dev activity (commit count / last merge from pbi-activity.json across repos).
- Merges of the day: today's dev-main commits per repo, grouped by PBI id (unlinked commits listed under "other").
- Attention flags: items in doing with no commits for several days, review items waiting, sync errors.
Save to reports/daily/<date>.html (overwrite same-day reruns), append an activity-log line, and give the user the path.

Changes

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.

1mo ago First seen · 39 lines · 62 tokens per session scan A 4f8602f657a1

Subscribe to this mod's changes

report-daily-progress is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 499 once invoked, about $0.0002 per session on Opus 5.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-09-03.

Analytics and metrics Claude Code Project management claude-code-plugin cross-platform desktop-app developer-tools obsidian

expo-launchpad-status

Show the current expo-launchpad pipeline state — phase, round, next role, pause reason — read-only.

SummerRiversound/expo-launchpad · 27 tokens

tasknotes

This skill should be used when the user asks to 'create a task', 'add a TODO', 'plan a sprint', 'organize tasks', 'track time', 'setup Kanban', 'create task from code', 'sync tasks with sprint', 'pomodoro session', 'start pomodoro', 'time estimate', or mentions TaskNotes, task management, or project planning in…

parisgroup-ai/imersao-ia-setup · 106 tokens

issue-hygiene

How to write an issue somebody can act on, how to triage a pile of them, and the label vocabulary that stays useful. Use when filing, triaging, labelling, closing or linking issues.

Mikedev115/Aetox · 47 tokens

aetox-slice

Decomposes a technical specification or plan into vertical tracer-bullet tickets. Calculates directed dependency graphs (DAG), schedules prefactoring first, applies expand-contract sequencing for wide refactors, quizzes the user on ticket granularity, and emits atomic per-ticket files sized for optimal agent context…

Mikedev115/Aetox · 64 tokens

project-consolidation

Safely consolidate drifted/duplicate project folders in the memex vault — cwd-fragment folders (e.g. Apps-arena, GitHub-loom), duplicate/split projects (one project's content scattered across two folders), and name-mismatch folders. Trigger on "consolidate project folders", "merge duplicate projects", "fix project…

linxule/memex-plugin · 133 tokens

roadmap-update

Produit un document de roadmap dans output/ en croisant l'état actuel des epics beads avec les décisions et priorités documentées dans le wiki. Applique les règles anti-lissage — ne jamais compléter avec des connaissances d'entraînement, citer le wiki pour chaque affirmation de scope ou de priorité. Triggers — mettre…

evb87-tech/corpus · 94 tokens