emit-tickets

emit-tickets is a skill for Claude Code, Codex from event4u-app/agent-config. It costs 42 tokens per session (1,679 once invoked), scanned A, original, MIT.

A planning tool that turns a roadmap into a bundle of buildable tickets, with one ticket for each workable step.

In plain words
What is it for?
It helps teams convert roadmaps into ticket files, split oversized steps, assign an appropriate work size, and check the resulting dependency graph.
Why use it?
It removes the manual effort of breaking a high-level plan into consistent tickets and checking that their dependencies are workable.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps teams convert roadmaps into ticket files, split oversized steps, assign an appropriate work size, and check the resulting dependency graph.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/event4u-app/agent-config/emit-tickets
Install

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.

Any agent
npx skills add event4u-app/agent-config --skill emit-tickets
Clone the repo
git clone --depth 1 https://github.com/event4u-app/agent-config

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for emit-tickets

README.md
[![agentmods](https://agentmods.dev/badge/skills/event4u-app/agent-config/emit-tickets/github.svg)](https://agentmods.dev/skills/event4u-app/agent-config/emit-tickets)
Your own site
<a href="https://agentmods.dev/skills/event4u-app/agent-config/emit-tickets"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/emit-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.

agentmods 80×15 button for emit-tickets

Your own site · 80×15
<a href="https://agentmods.dev/skills/event4u-app/agent-config/emit-tickets"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/emit-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,679 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01679
Opus 5 $0.00021 $0.00839
Sonnet 5 $0.00008 $0.00336
Haiku 4.5 $0.00004 $0.00168

Measured 7d ago against content hash 0971f2677d21, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

emit-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 7d 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.

src/skills/emit-tickets/SKILL.md · 199 lines

How it starts

The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.

emit-tickets

Materialise a roadmap into an agents/tickets/{slug}/ bundle — one ticket per buildable step — then wire the markers back and run the buildability gate.

When to use

Signal Match
"turn this roadmap into tickets" yes
"materialise / emit tickets for <roadmap>" yes
"mach Tickets aus der Roadmap" yes
"plan the work for <roadmap>" yes
User wants a YAML ticket bundle, not a prose plan yes
Refining or splitting an existing ticket no → use refine-ticket
Estimating a single ticket no → use estimate-ticket

Upstream: roadmap-writing — author the roadmap first. Downstream: src/scripts/lint_ticket_buildable.ts (the build-readiness gate). A ticket reaches a tracker by paste or MCP (ADR-102) — no export script.

Procedure

Steps at a glance:

  1. Locate and parse the roadmap.
  2. Create agents/tickets/{slug}/ and draft one ticket YAML per materializable step.
  3. Assign model_tier via the granularity floor; split oversized steps.
  4. Compute SHA refs for adr_refs / source_refs.
  5. Write manifest.yml with acyclic dependency_graph and empty linear_state.
  6. Append <!-- ticket: T-NNN --> markers back into the roadmap.
  7. (Re)generate agents/tickets/_registry.yml.
  8. Run lint_ticket_buildable until exit 0 (max 3 attempts).
  9. Tell the user the bundle is ready: paste a ticket into Linear/Jira, or have the agent create it via a tracker MCP server (ADR-102 — no API export).

§0 — Locate the roadmap

Confirm the roadmap slug and open agents/roadmaps/{slug}.md. Identify all materializable steps (checkbox items that describe a code or docs change). Skip informational steps, phase headings, and acceptance-criteria prose.

§1 — Derive the bundle slug

agents/tickets/{slug}/ — same slug as the roadmap. Create the directory.

§2 — One ticket per step

For each materializable step, draft a ticket YAML:

id: T-NNN
roadmap: {slug}
phase: {N}
title: "{step text, ≤80 chars}"
status: ready
model_tier: {lite | medium | high}   # see §3
estimate: {story-points, integer}
priority: {1=critical … 4=low}
labels: []
parent: null
blocked_by: []
adr_refs: []
source_refs: []
assets: none
acceptance:
  - "{measurable done criterion}"
boundaries:
  must_touch: []
  may_touch: []
  must_not_touch: []

Read the full file on GitHub · 199 lines

Changes

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.

  1. 7d ago First seen · 199 lines · 42 tokens per session scan A 0971f2677d21

Subscribe to this mod's changes

emit-tickets is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,679 once invoked, about $0.0002 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.