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.
git 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/plugins/andkirby/markdown-ticket/mdt)<a href="https://agentmods.dev/plugins/andkirby/markdown-ticket/mdt"><img src="https://agentmods.dev/badge/plugins/andkirby/markdown-ticket/mdt/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/plugins/andkirby/markdown-ticket/mdt"><img src="https://agentmods.dev/badge/plugins/andkirby/markdown-ticket/mdt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mdt 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 1mo 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
{
"version": "0.11.1-beta",
"name": "mdt",
"description": "MDT (Markdown Ticket) workflow commands - CR creation, requirements, BDD, architecture, testing, tasks, implementation with agentic verification, technical debt detection, and workflow suggestions",
"author": {
"name": "andkirby"
},
"keywords": [
"tickets",
"kanban",
"markdown",
"workflow",
"tdd",
"bdd",
"requirements"
],
"commands": [
"./commands/architecture.md",
"./commands/assess.md",
"./commands/bdd.md",
"./commands/clarification.md",
"./commands/domain-audit.md",
"./commands/domain-lens.md",
"./commands/poc.md",
"./commands/reflection.md",
"./commands/requirements.md",
"./commands/suggest.md",
"./commands/tech-debt.md",
"./commands/tests.md",
"./commands/ticket-creation.md",
"./commands/tasks.md",
"./commands/implement-agentic.md",
"./commands/implement.md"
],
"agents": [
"./agents/cmd-agent.md",
"./agents/verify.md",
"./agents/code.md",
"./agents/fix.md",
"./agents/verify-complete.md"
]
}
What it installs
The manifest is a name and a version. 1 skill, 16 commands, 5 agents, 1 hook travel with it, and installing the plugin installs all of them — 189 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill mdt A 96 tokens
- Command domain-audit A 0 tokens
- Command implement-agentic A 9 tokens
- Command bdd A 0 tokens
- Command clarification A 0 tokens
- Command poc A 0 tokens
- Command tasks A 0 tokens
- Command architecture A 0 tokens
- Command assess A 0 tokens
- Command domain-lens A 0 tokens
- Command implement A 0 tokens
- Command requirements A 0 tokens
- Command reflection A 0 tokens
- Command suggest A 8 tokens
- Command tech-debt A 0 tokens
- Command tests A 0 tokens
- Command ticket-creation A 0 tokens
- Agent verify-complete A 19 tokens
- Agent code A 17 tokens
- Agent verify A 12 tokens
- Agent fix A 16 tokens
- Agent cmd-agent A 12 tokens
- Hook Stop A not measured
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.
- 1mo ago First seen · 43 lines scan A 47bfa90c51f7
mdt is a plugin published in the GitHub repository andkirby/markdown-ticket (7 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.