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 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/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/radutopala/ticket/tk"><img src="https://agentmods.dev/badge/skills/radutopala/ticket/tk.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.00009 | $0.00569 |
| Opus 5.5 | $0.00004 | $0.00228 |
| Sonnet 5.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 2mo 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.
- 2mo ago First seen · 84 lines · 9 tokens per session scan A 413ece83edcb
tk is a skill published in the GitHub repository radutopala/ticket (8 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 569 once invoked, about $0.0000 per session on Opus 5.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
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
code2prompt
Explore codebases efficiently with code2prompt, using sem-backed entity maps and grouped source reads to reduce agent round trips. Use when understanding an unfamiliar repository, locating implementations, gathering context for changes or reviews, or installing code2prompt.
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
summarize-releases
Create a monthly NVIDIA Elements “What’s New” docs page, matching video, and concise, copy-ready summary from local release tags, tagged changelogs, package versions, and commit history. Use for a scheduled release PR, monthly update, release roundup, changelog digest, Slack blurb, announcement, or plain-language…
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.