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 agentmods add skills/radutopala/ticket/tknpx skills add radutopala/ticket --skill tkgit clone --depth 1 https://github.com/radutopala/ticketWrote 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/radutopala/ticket/tk)<a href="https://agentmods.dev/skills/radutopala/ticket/tk"><img src="https://agentmods.dev/badge/skills/radutopala/ticket/tk.svg" alt="Measured on agentmods" 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 | $0.00009 | $0.00569 |
| Opus 5 | $0.00005 | $0.00284 |
| Sonnet 5 | $0.00002 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
tk 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tk - Ticket Management
A minimal CLI for tracking tickets as markdown files in .tickets/.
Workflow
tk ready # 1. Find available work
tk start <id> # 2. Claim a ticket
tk show <id> # 3. Read details
# ... do the work
tk close <id> # 4. Mark complete
Core Commands
| Command | Description |
|---|---|
tk create "title" |
Create ticket (returns ID) |
tk show <id> |
View ticket details |
tk start <id> |
Claim ticket (set to in_progress) |
tk close <id> |
Complete ticket |
tk reopen <id> |
Revert to open |
tk edit <id> |
Open in $EDITOR |
Listing & Filtering
tk list # All tickets
tk list --status open # By status (open|in_progress|closed)
tk list -a alice # By assignee
tk list -T urgent # By tag
tk ready # Open tickets with resolved deps
tk blocked # Tickets with unresolved deps
tk closed # Recently closed
Create Options
tk create "Fix login bug" \
-d "Description text" \
-t bug \ # Type: bug|feature|task|epic|chore
-p 1 \ # Priority: 0-4 (0=highest)
-a alice \ # Assignee
--parent <epic-id> \ # Parent ticket
--tags ui,urgent # Tags
Dependencies
tk dep add <id> <depends-on> # Add dependency
tk dep remove <id> <dep-id> # Remove dependency
tk dep tree # Show dependency tree
tk dep check # Check for cycles
Notes & Links
tk add-note <id> "Progress update" # Add timestamped note
tk link <id1> <id2> # Link related tickets
tk unlink <id1> <id2> # Remove link
Export
tk query # JSON output
tk query '.[] | .title' # With jq filter
Tips
- Partial ID matching:
tk show a1bmatchestic-a1b2c3 - Tickets stored in
.tickets/as markdown with YAML frontmatter - Git-friendly: commit tickets with your code
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.
- 4d ago First seen · 84 lines · 9 tokens per session scan A 413ece83edcb
tk is a skill published in the GitHub repository radutopala/ticket (5 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 569 once invoked, about $0.0000 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
bubbletea
Browse Bubbletea TUI framework documentation and examples. Use when working with Bubbletea components, models, commands, or building terminal user interfaces in Go.
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
pinchtab-stealth-score
Run the PinchTab stealth-score sweep against 15 bot-detection / fingerprint sites (sannysoft, rebrowser, deviceandbrowserinfo, iphey, whoer, browserscan, pixelscan, fingerprint-scan, incolumitas, fvision, amiunique, browserleaks, creepjs, coveryourtracks, fingerprint-demo). Starts a Docker PinchTab container per…
gmeasure
Benchmark and measure Go code with gmeasure — an Experiment groups named Measurements, recorded via RecordValue/RecordDuration/MeasureDuration or repeated Sample/SampleValue/SampleDuration with SamplingConfig, timed inline with a Stopwatch, summarized through GetStats/Stats (StatMin/Max/Mean/Median/StdDev…
markstream-react
Integrate the beta markstream-react package into a React 18+ or Next app. Use when Codex needs to add the React renderer, choose the root, next, or server entrypoint, import CSS correctly, choose between content and nodes, keep client boundaries safe, add renderer-local streamingComponents or htmlComponents, use…