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 jeremylongworth-source/AgentSkills --skill deliverables-trackergit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/deliverables-tracker)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/deliverables-tracker"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/deliverables-tracker/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.
<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/deliverables-tracker"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/deliverables-tracker.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.00324 |
| Opus 5.5 | $0.00021 | $0.00130 |
| Sonnet 5.5 | $0.00011 | $0.00065 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
deliverables-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 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.
What it actually says
Deliverables Tracker
Core Workflow
- Identify sponsor, campaign, deliverables, owners, due dates, approval flow, links, assets, usage terms, reporting, and invoice milestones.
- Build a tracker with status, next action, blocker, approval owner, and due date for each deliverable.
- Include required disclosure, rights, caption, link, metadata, and proof checks before publish.
- Add post-publish links, reporting dates, and recap requirements.
- Flag overdue, blocked, ambiguous, or high-risk items.
- Keep the tracker read-only unless the user approves updates to external systems.
Safety Rules
- Do not publish, schedule, invoice, or mark sponsor approval without explicit confirmation.
- Do not invent approval status, live links, performance data, or payment status.
- Flag missing disclosure, rights, claims, and approval evidence.
Deliverable Shape
For deliverables trackers, provide:
- Campaign summary
- Tracker table
- Required checks
- Blockers and risks
- Next actions
- Reporting and invoice notes
- Approval owner
References
- Read
references/deliverables-tracker-checklist.mdwhen creating sponsor deliverables trackers.
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.
- 1mo ago First seen · 46 lines · 53 tokens per session scan A 53d2dc9cbd92
deliverables-tracker is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 53 tokens to every session and 324 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.
Other skills, from other repositories
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
handing-off-work
Hands off unfinished work with a closed-loop briefing of state, changed conditions, remaining scope, authority limits, and open evidence. Use when AI-agent, reviewer, verifier, releaser, or resumed-thread work transfers to a new owner. Do not use when the same owner continues uninterrupted with full context.
analiz-task-spec
Use when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand over.
answer-workspace-questions
Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval.
call-prep
Create or review call prep deliverables with traceable assumptions, decision criteria, ownership, and risk controls. Use when the user asks for call prep planning or analysis.