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 event4u-app/agent-config --skill emit-ticketsgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/emit-tickets)<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.
<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>- NVIDIA SkillSpector pass
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.00042 | $0.01679 |
| Opus 5 | $0.00021 | $0.00839 |
| Sonnet 5 | $0.00008 | $0.00336 |
| Haiku 4.5 | $0.00004 | $0.00168 |
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.
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:
- Locate and parse the roadmap.
- Create
agents/tickets/{slug}/and draft one ticket YAML per materializable step. - Assign
model_tiervia the granularity floor; split oversized steps. - Compute SHA refs for
adr_refs/source_refs. - Write
manifest.ymlwith acyclicdependency_graphand emptylinear_state. - Append
<!-- ticket: T-NNN -->markers back into the roadmap. - (Re)generate
agents/tickets/_registry.yml. - Run
lint_ticket_buildableuntil exit 0 (max 3 attempts). - 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: []
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.
- 7d ago First seen · 199 lines · 42 tokens per session scan A 0971f2677d21
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.
Other skills, from other repositories
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
pad
Talk to your project. Natural-language project management — create items, check status, plan work, brainstorm ideas, and more.
pm-arch
Skill "pm-arch" from wei63w/pm-manager, covering user input, outline, done when and shared workflow (all /pm- commands).
pm-discover
Skill "pm-discover" from wei63w/pm-manager, covering user input, outline and shared workflow.