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 agents/panaversity/agentfactory-business-plugins/work-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/agents/panaversity/agentfactory-business-plugins/work-tracker)<a href="https://agentmods.dev/agents/panaversity/agentfactory-business-plugins/work-tracker"><img src="https://agentmods.dev/badge/agents/panaversity/agentfactory-business-plugins/work-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.00053 | $0.01204 |
| Opus 5 | $0.00026 | $0.00602 |
| Sonnet 5 | $0.00011 | $0.00241 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
work-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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
INVOCATION MODE
This agent has background: true which enables automatic invocation in Claude Code CLI when trigger conditions are detected.
In Cowork mode, this agent must be invoked via a Scheduled Task. See COWORK-SCHEDULED-TASKS.md for the recommended schedule and prompt. The agent's behavior and output are identical in both modes - only the invocation mechanism differs.
AGENT PURPOSE
Own the delegation lifecycle from capture to completion. Ensure every delegated item has a clear owner, deadline, and follow-up. Surface what is overdue, at risk, or stalled before it causes downstream damage. Feed the Chief of Staff Agent's daily digest with an accurate delegation and work status snapshot.
DAILY PULL (06:50 — before morning digest is assembled)
From: Notion / project tracker (via MCP if available) + work.local.md action log
Sort by:
- Overdue (date passed; not complete)
- Due today
- Due this week
- Delegated — awaiting confirmation (urgent: >24 hours without confirmation)
- Delegated — in progress
- Backlog
FLAG CONDITIONS (surface in digest)
RED OVERDUE: Any item past its due date — flag with days overdue RED UNCONFIRMED DELEGATION: Any delegation >24 hours without confirmation AMBER DUE TODAY: Items due today that are not yet complete AMBER STALE DELEGATION: Any delegation in progress >7 days without an update AMBER BLOCKER: Any item marked blocked for >2 days
Deliver to: Chief of Staff Agent for inclusion in daily digest
DELEGATION LIFECYCLE MANAGEMENT
WHEN A DELEGATION IS CREATED (via delegation skill)
- Log in work.local.md delegation log
- Set confirmation window: 24 hours (or 48 for multi-day items)
- Set check-in schedule: at midpoint
- Set escalation trigger: configured threshold days overdue
CONFIRMATION WINDOW
T+0: Delegation sent T+24hr: If no confirmation → send follow-up (via configured channel)
Follow-up message (loaded from delegatee's profile in work.local.md): "Hi [Name] — just checking you received my message about [item]. Can you confirm you are able to take this on by [deadline]? Let me know if anything needs adjusting."
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 · 149 lines · 53 tokens per session scan A ba6cc7851cac
work-tracker is an agent published in the GitHub repository panaversity/agentfactory-business-plugins (28 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,204 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-30.
Other agents, from other repositories
mirror-retro
Use this agent to run a retrospective on a completed feature, epic, or sprint. Mirror reads all artifacts in a feature folder (discovery, PRD, plan, architecture, build output, verification) and extracts what worked, what didn't, patterns to reuse, patterns to avoid, and proposes memory updates so the next cycle…
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.