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 lttr/claude-marketplace --skill ticketgit clone --depth 1 https://github.com/lttr/claude-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/skills/lttr/claude-marketplace/ticket)<a href="https://agentmods.dev/skills/lttr/claude-marketplace/ticket"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/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/skills/lttr/claude-marketplace/ticket"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/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.00053 | $0.00326 |
| Opus 5 | $0.00026 | $0.00163 |
| Sonnet 5 | $0.00011 | $0.00065 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
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 11d 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.
What it actually says
Ticket
Update Azure DevOps work item state via az boards work-item update.
Input Format
$ARGUMENTS = <id> <state>.
| Synonym | Azure DevOps state |
|---|---|
active, start, in-progress |
Active |
cr, code-review, review |
Code Review |
ready, done-dev |
Ready |
closed, done, complete |
Closed |
Unknown state → ask user. Missing id → ask. Missing state → ask.
Workflow
1. Parse + map state
Extract id (numeric) and state synonym. Map to canonical Azure DevOps state.
2. Update
az boards work-item update --id <id> --state "<State>"
3. Confirm
Print: work item id, title, new state.
Notes
- States above match the most common Azure DevOps process templates. If your project uses different state names (e.g.
Doing,In Review), pass the exact label. - Branch creation lives in the
feature-branchskill — keeps state changes orthogonal.
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.
- 11d ago First seen · 43 lines · 53 tokens per session scan A d87b726699c7
ticket is a skill published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 326 once invoked, about $0.0003 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 skills, from other repositories
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
multi-agent
A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
project-execution
Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.
to-issues
A planning aid that breaks a PRD or technical specification into small implementation issues, each covering a complete, demonstrable piece of work.