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.
git clone --depth 1 https://github.com/hg-pyun/claude-code-marketplaceWrote 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/commands/hg-pyun/claude-code-marketplace/enrich-ticket)<a href="https://agentmods.dev/commands/hg-pyun/claude-code-marketplace/enrich-ticket"><img src="https://agentmods.dev/badge/commands/hg-pyun/claude-code-marketplace/enrich-ticket/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/commands/hg-pyun/claude-code-marketplace/enrich-ticket"><img src="https://agentmods.dev/badge/commands/hg-pyun/claude-code-marketplace/enrich-ticket.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.00126 | $0.01500 |
| Opus 5 | $0.00063 | $0.00750 |
| Sonnet 5 | $0.00025 | $0.00300 |
| Haiku 4.5 | $0.00013 | $0.00150 |
Grade A, and why
enrich-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 12d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- User shares a Linear ticket URL and wants it enriched ("이 티켓 채워줘", "enrich this ticket")
- A ticket has a one-line title but no detail and the user wants help structuring it
- The user invokes
/enrich-ticket <url> - A new ticket needs acceptance criteria, technical detail, or context the original creator did not provide </Use_When>
<Do_Not_Use_When>
- User wants to read a ticket — use Linear MCP
get_issuedirectly - User wants to create a brand-new ticket from scratch with no existing reference — use a different flow
- User is asking conceptual Linear questions
- The ticket is already complete (description, acceptance criteria, technical notes all present) </Do_Not_Use_When>
<Why_This_Exists> Many Linear tickets ship as "fix the login bug" — true but unactionable. A focused interview (technical implementation, UI/UX considerations, tradeoffs, edge cases) produces a ticket that a downstream engineer can act on without rediscovering context. The skill writes results back to the source of truth (Linear), not to a side document, so the next person reading the ticket sees the complete version. </Why_This_Exists>
<Execution_Policy>
- Interview questions and ticket content written to Linear are both written in
$LANGUAGE. - Use
AskUserQuestionfor the interview — one question at a time, never batched. - Continue until the ticket has enough detail that an engineer could start work without further clarification.
- Use Linear MCP for reading and writing the ticket; do not paste content into chat as a substitute.
- Do not invent technical details the user did not confirm; if a question is unresolved, mark it explicitly in the ticket body. </Execution_Policy>
<Settings_Reference>
$LANGUAGE: the language setting fromplugin.jsonsettings.language(defaultKorean). Override with--lang=<value>. Presets: Korean, English, Japanese, Chinese. Custom values accepted. </Settings_Reference>
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.
- 12d ago First seen · 136 lines · 126 tokens per session scan A ac083b05d58c
enrich-ticket is a command published in the GitHub repository hg-pyun/claude-code-marketplace (2 stars, last pushed 2mo ago), licensed MIT. It adds 126 tokens to every session and 1,500 once invoked, about $0.0006 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-08-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.