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 andkirby/markdown-ticket --skill mdt-cligit clone --depth 1 https://github.com/andkirby/markdown-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/andkirby/markdown-ticket/mdt-cli)<a href="https://agentmods.dev/skills/andkirby/markdown-ticket/mdt-cli"><img src="https://agentmods.dev/badge/skills/andkirby/markdown-ticket/mdt-cli/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/andkirby/markdown-ticket/mdt-cli"><img src="https://agentmods.dev/badge/skills/andkirby/markdown-ticket/mdt-cli.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.00100 | $0.02597 |
| Opus 5.5 | $0.00040 | $0.01039 |
| Sonnet 5.5 | $0.00020 | $0.00519 |
| Haiku 4.5 | $0.00010 | $0.00260 |
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 28d 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 — 234 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.
Project Resolution
Commands resolve the project from the cwd: the nearest .mdt-config.toml
walking up from the current directory, with a registry fallback. Inside a
project, omit -p — cwd detection is the default and the recommended path.
Use -p <code> only to target a different project than cwd, and
mdt-cli project ls only for cross-project work or when cwd is not inside a
project. Do not list all projects just to orient — run bare mdt-cli project
for the current project's info.
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
mdt-cli ticket get -p <code> <key> # Resolve within an explicit project (any cwd)
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.
-p, --project <code> — resolve the ticket within the given project instead of the cwd-detected one; explicit project wins over key-embedded codes. Unknown project → Project <code> not found, exit 1. Useful for non-interactive consumers running outside a project root.
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
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.
- 28d ago Changed · +17 lines ce7deb4954ff
- 1mo 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 (7 stars, last pushed 3d ago), licensed MIT. It adds 100 tokens to every session and 2,597 once invoked, about $0.0004 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.