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 estimate-ticketgit 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/estimate-ticket)<a href="https://agentmods.dev/skills/event4u-app/agent-config/estimate-ticket"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/estimate-ticket.svg" alt="Measured on agentmods" 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.00049 | $0.01986 |
| Opus 5 | $0.00024 | $0.00993 |
| Sonnet 5 | $0.00010 | $0.00397 |
| Haiku 4.5 | $0.00005 | $0.00199 |
Grade A, and why
estimate-ticket 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 5d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Estimate Ticket
Sibling of
/refine-ticket. Takes the same input, returns size, risk, split recommendation, and uncertainty — nothing else. Separate from refinement so each stays sharp. Output is copyable; write-back is user-gated.
When to use
- Sprint planning: "how big is PROJ-123?"
- Scope sanity: "should we split this?"
- Confidence check: "do we actually understand this ticket?"
- German: "wie groß ist das Ticket?", "sollen wir das splitten?", "ist das ein Spike-Kandidat?"
When NOT to use (near-misses)
| Phrasing | Route to |
|---|---|
| "refine the ticket" / "tighten AC" | /refine-ticket (sibling) |
| "plan this feature" | /feature-plan (downstream) |
| "is this a duplicate?" | validate-feature-fit (sub-skill) |
| "threat-model this" | threat-modeling (sub-skill) |
| "investigate this bug" | /bug-investigate |
/estimate-ticket does not rewrite the ticket. If the ticket is
too vague to estimate, output says so and routes to /refine-ticket.
Inputs
Same four paths as /refine-ticket (delegates to jira-ticket loader):
ticket key, branch-name detection, pasted text, URL.
Procedure
1. Load ticket
Delegate to jira-ticket §1-3 (key / URL / branch → Jira API fetch,
summary + description + AC + comments). For pasted text: parse markdown.
2. Inspect estimability
Before producing numbers, check:
- Is the outcome observable (AC bullets concrete)?
- Is the scope one behavior, or bundled?
- Are external dependencies (APIs, teams, migrations) named?
- Is there a rollback plan implied?
If the ticket scores low on estimability (vague AC, no out-of-scope,
no mention of dependencies), set uncertainty = Underspecified and
emit a single-line redirect to /refine-ticket at the top of the output.
A cross-source discrepancy (per cross-source-consistency, gated by consistency.cross_source) — ticket text contradicting an attached mockup, or a clearly-needed-but-unstated behavior (weekend/holiday shift) — is not estimable as-is: it hides an open scope decision. Raise uncertainty and name the discrepancy in the redirect rather than sizing over a contradiction.
What ships with it
3 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.
- 5d ago First seen · 200 lines · 49 tokens per session scan A d2a0701917a9
estimate-ticket is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 1,986 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.