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.
/plugin marketplace add atman-33/workhub/plugin install team-opsWrote 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/atman-33/workhub/report-daily-progress)<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="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.00062 | $0.00499 |
| Opus 5 | $0.00031 | $0.00249 |
| Sonnet 5 | $0.00012 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
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 4d 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.
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'sscope.json+planning.md(for scope-change notes), and each repo'spbi-activity.json+commits.jsonltail (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.jsontotal points → 0 over the sprint dates vs actualsprintRemainingPointsper 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.jsonacross 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
doingwith no commits for several days,reviewitems waiting, sync errors.
-
Save to
reports/daily/<date>.html(overwrite same-day reruns), append an activity-log line, and give the user the path.
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.
- 4d ago First seen · 39 lines · 62 tokens per session scan A 4f8602f657a1
report-daily-progress is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 499 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-09-03.
Other skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
shipyard-executing-plans
Use when you have a written implementation plan to execute, either in the current session with builder/reviewer agents or in a separate session with review checkpoints. Also use when the user says "build this", "implement this", "execute the plan", "run the plan", or when a plan file has been loaded with independent…
shipyard-writing-plans
Use when you have a spec, requirements, or design for a multi-step task — before touching code. Also triggers on "plan this", "break this down", "create tasks", "decompose this feature", or when a task clearly needs more than 2-3 steps to implement. If you're about to start building without a plan, or writing vague…
shipyard-handoff
Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
roadmap
An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.