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/panaversity/agentfactory-business-plugins/progress-trackernpx skills add panaversity/agentfactory-business-plugins --skill progress-trackergit clone --depth 1 https://github.com/panaversity/agentfactory-business-pluginsWrote 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/panaversity/agentfactory-business-plugins/progress-tracker)<a href="https://agentmods.dev/skills/panaversity/agentfactory-business-plugins/progress-tracker"><img src="https://agentmods.dev/badge/skills/panaversity/agentfactory-business-plugins/progress-tracker.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 | $0.00085 | $0.01169 |
| Opus 5 | $0.00043 | $0.00584 |
| Sonnet 5 | $0.00017 | $0.00234 |
| Haiku 4.5 | $0.00009 | $0.00117 |
Grade A, and why
progress-tracker 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROGRESS TRACKING AND DASHBOARD WORKFLOW
STEP 1 — LOAD CONTEXT
Read work.local.md in the current working directory.
If it does not exist, tell the user to run /agentic-office:setup first.
Load dashboard configuration from work.local.md dashboard: section.
STEP 2 — IDENTIFY REQUEST TYPE
TYPE 1: WEEKLY STATUS (across all projects) Output: RAG status per project; current milestone; this week's action; critical path; open delegations
TYPE 2: PROJECT MILESTONE PLAN Output: Full milestone breakdown for a project with owners and dates
TYPE 3: BLOCKER IDENTIFICATION Output: All blockers across all projects; who owns resolving each; escalation recommendation if stalled
TYPE 4: COMPLETION SUMMARY Output: What was completed this week/period; what the impact was; what carries forward
TYPE 5: EXECUTIVE DASHBOARD Output: Full cross-domain dashboard view
STEP 3 — PRODUCE OUTPUT
Weekly Status Output
WEEKLY PROJECT STATUS — Week of [Date]
================================================================
-- [PROJECT NAME] ([Priority]) ----------------------------------
Status: [GREEN/AMBER/RED] [ONE-LINE STATUS]
This week: [Current milestone or activity]
Next: [Next milestone; due date]
Risk: [What could derail — be specific; not "general risk"]
This week's action: [The one thing that moves this forward most]
Open delegations: [Any delegated items affecting this project]
-- CRITICAL PATH (this week) ------------------------------------
[The 3-5 items that, if done, make the week a success]
1. [Item] — [Owner] — [Due]
2. [Item] — [Owner] — [Due]
-- BLOCKERS ------------------------------------------------------
RED [Project]: [What is blocked] — [Who owns unblocking] — [Days blocked]
[Escalation recommended if blocked >7 days]
================================================================
Milestone Plan Format
MILESTONE PLAN: [Project Name]
Owner: [Name] | Priority: [P1/P2/P3] | Target: [End date]
------------------------------------------------------------
MILESTONE 1: [Name]
Due: [Date]
Owner: [Person]
Done when: [Specific deliverable or outcome]
Dependencies: [What must be true before this can complete]
Status: [NOT STARTED / IN PROGRESS / AT RISK / COMPLETE]
[Repeat for each milestone]
------------------------------------------------------------
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 156 lines · 85 tokens per session scan A f85548ae41e0
progress-tracker is a skill published in the GitHub repository panaversity/agentfactory-business-plugins (28 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 1,169 once invoked, about $0.0004 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
kanban-codex-lane
Use when a Hermes Kanban worker wants to run Codex CLI as an isolated implementation lane while Hermes keeps ownership of task lifecycle, reconciliation, testing, and handoff.
kanban
Hermes Kanban multi-agent workflow — orchestrator decomposition playbook and worker pitfalls/examples for routing work across profiles through the durable SQLite board.
codebase-audit-and-roadmap
Audit a codebase from a user reference and produce a structured feature inventory, gap analysis, and build-plan PRD.
prd-review-framework
Use when reviewing a PRD for goal clarity, scope, assumptions, and implementation readiness.
content-production-workflow
End-to-end workflow for creative review gates, content drafting, and publishing to blogs, Notion, and social channels with explicit approval checkpoints.
client-success-and-retention
Use when designing client delivery for a coaching/agency program, hiring or running a Client Success Manager / success coach, handling a struggling or refund-requesting client, setting onboarding-call and check-in cadence, improving retention and continuity, or building/optimising a booking confirmation page (the…