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 fabricepayet/skills --skill delivery-ticketsgit clone --depth 1 https://github.com/fabricepayet/skillsWrote 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/fabricepayet/skills/delivery-tickets)<a href="https://agentmods.dev/skills/fabricepayet/skills/delivery-tickets"><img src="https://agentmods.dev/badge/skills/fabricepayet/skills/delivery-tickets/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/fabricepayet/skills/delivery-tickets"><img src="https://agentmods.dev/badge/skills/fabricepayet/skills/delivery-tickets.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.00021 | $0.01194 |
| Opus 5.5 | $0.00008 | $0.00478 |
| Sonnet 5.5 | $0.00004 | $0.00239 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
delivery-tickets 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delivery Tickets
Purpose
Produce a dependency graph of tracer-bullet vertical slices and publish it when authorized. Each delivery ticket makes one narrow, complete behavior independently demonstrable or verifiable while preserving traceability to approved product and technical decisions.
Scope and authority
- A planning request is complete when the proposed graph is returned for review, with any gaps identified; it does not require approval of that graph.
- Creating or updating tracker tickets requires explicit publication authorization in the current request or established task scope. Engineering approval confirms the graph; it does not authorize external mutations by itself. Reuse approval of the unchanged graph.
Tracker resolution
Use the tracker designated for the consuming project: current user instructions, then applicable AGENTS.md / CLAUDE.md and their references, then CONTRIBUTING.md, then README.md. A Git host or installed connector alone does not designate a tracker. Reuse established choices and project conventions; resolve conflicts by instruction scope.
Drafting needs no tracker. Before a tracked operation, ask only for the missing destination or information needed for that operation. No setup skill or fixed configuration path is required.
Artifact references
Use complete inputs from the conversation, supplied files, or the tracker, with stable references, exact versions, and evidenced approval where required. Check currency at the authoritative source; conversation-only inputs need no tracker access. Ask for unavailable content or evidence rather than inventing it. If publication depends on unpublished parents, plan their publication and reference mapping within the user's authorization.
Input gate
Require exact references and versions for:
- one current Product Contract with status
Product Approved; - one current Technical Design with status
Technical Approvedthat names that Product Contract version.
Stop when either artifact is missing, unapproved, superseded, or mismatched. Delivery planning cannot complete product or technical design.
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 Changed · +1 lines · -7 tokens per session 29ba7454612e
- 2mo ago First seen · 88 lines · 28 tokens per session scan A 92071c385bf5
delivery-tickets is a skill published in the GitHub repository fabricepayet/skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,194 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
dev-console-context
Use when the user mentions Developer Console, projects, workspaces, credentials, or orgs — or uses phrases like "show my projects", "list workspaces", "get credentials", "switch project", "which org", "my org", "console", "navigate", "explore", "what projects do I have", "show credentials", "what workspace". Also use…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.