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.
/plugin marketplace add andkirby/markdown-ticketnpx agentmods add plugins/andkirby/markdown-ticket/mdtgit clone --depth 1 https://github.com/andkirby/markdown-ticketGrade 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 yesterday.
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 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.
- yesterday First seen · 43 lines scan A 47bfa90c51f7
mdt is a plugin published in the GitHub repository andkirby/markdown-ticket (5 stars, last pushed 16d 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
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.