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/andkirby/markdown-ticket/mdt-clinpx skills add andkirby/markdown-ticket --skill mdt-cligit clone --depth 1 https://github.com/andkirby/markdown-ticketWhat 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.00100 | $0.02241 |
| Opus 5 | $0.00050 | $0.01120 |
| Sonnet 5 | $0.00020 | $0.00448 |
| Haiku 4.5 | $0.00010 | $0.00224 |
Grade A, and why
mdt-cli 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 3d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mdt-cli CLI
Terminal tool for Markdown Ticket management. Binary: mdt-cli.
Key Resolution
All ticket commands accept flexible key forms:
| Input | Resolves to |
|---|---|
12 |
{PROJECT}-012 (from detected project) |
ABC-12 |
ABC-012 (normalized, cross-project) |
Bare numbers and full keys can be used directly: mdt-cli 12 views the ticket.
View
mdt-cli <key> # Bare shortcut
mdt-cli ticket get <key> # Canonical form
Prints ticket title, labeled metadata (status, type, priority, phase, assignee, dates), and path. If the ticket has a CR directory with subdocuments, lists them below the path.
List
mdt-cli list # Shortcut
mdt-cli ls # Shortcut
mdt-cli ticket list # Canonical form
mdt-cli ticket list --project <code> # List another project's tickets
Shows up to 10 tickets sorted newest-first. Each ticket shows key + title on one line, then an indented metadata row.
Options:
--all— show every ticket--limit N— override default count--files— file paths only--info— ticket info without paths--json— parseable output for LLM consumption-p, --project <code>— list tickets from a different project
Filters — positional key=value args with AND across fields, comma-separated fuzzy match within a field:
mdt-cli list status=impl priority=high,critical
Filterable fields: status, priority, type, level, assignee, epic/phase. (level accepts aliases: e→epic, t→ticket.)
Create
mdt-cli create <type>[/<priority>] '<title>' [slug]
mdt-cli ticket create --project <code> feature 'Add dark mode'
mdt-cli ticket create --stdin feature 'Add dark mode' <<'EOF'
## Problem
Users need a dark theme option.
EOF
For an enabled [project.cloudSync] binding, ticket create uses the shared
cloud coordinator automatically. It requires a live Access credential and does
not allocate a local fallback number. Dedicated cloud project/member management
commands are owned by MDT-202.
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.
- 3d ago First seen · 217 lines · 100 tokens per session scan A eac1c3bd285f
mdt-cli is a skill published in the GitHub repository andkirby/markdown-ticket (5 stars, last pushed 17d ago), licensed MIT. It adds 100 tokens to every session and 2,241 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…