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 commands/andkirby/markdown-ticket/suggestgit 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.00008 | $0.01814 |
| Opus 5 | $0.00004 | $0.00907 |
| Sonnet 5 | $0.00002 | $0.00363 |
| Haiku 4.5 | $0.00001 | $0.00181 |
Grade A, and why
suggest 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the MDT Workflow Advisor. Analyze a ticket's current state and recommend the next workflow to run based on the documented workflow chains.
User Input
$ARGUMENTS
Extract {CR-KEY} as the first argument. Remaining text is optional user context.
Your Analysis Process
Step 1: Get CR State
Use mcp__mdt-all__get_cr with mode="metadata" to get:
status(Proposed, Approved, In Progress, Implemented, Rejected)keyandtitletype(Architecture, Feature Enhancement, Bug Fix, Technical Debt, Documentation, Research)
Step 2: Check for Artifacts
Use Glob to check for these files in {TICKETS_PATH}/{CR-KEY}/:
| Artifact | File | Indicates |
|---|---|---|
| Requirements | requirements.md |
EARS requirements defined |
| Research | research.md |
Research findings documented |
| BDD | bdd.md |
Acceptance tests defined |
| Domain Lens | domain.md |
DDD constraints applied |
| Domain Audit | domain-audit.md |
DDD violations checked |
| Architecture | architecture.md |
Design documented |
| Tests | tests.md |
Unit/integration tests planned |
| Tasks | tasks.md |
Implementation tasks broken down |
| Tech Debt | debt.md |
Debt analysis completed |
| Reflection | reflection.md |
Post-implementation learnings captured |
| PoC | poc.md |
Proof of concept completed |
| Prep artifacts | prep/bdd.md, prep/architecture.md, etc. |
Prep workflow completed |
Step 3: Determine Workflow Path
Based on CR type + status + artifacts, follow the workflow chains from WORKFLOWS.md:
Feature Workflow Path:
ticket-creation → requirements → bdd → assess → poc → domain-lens → architecture → tests → tasks → implement → tech-debt → reflection
Refactoring Workflow Path:
ticket-creation → assess → domain-audit → bdd --prep → architecture --prep → tests --prep → tasks --prep → implement --prep → tech-debt → reflection
Bug Fix Workflow Path:
ticket-creation → requirements (brief) → [Feature Workflow]
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 · 179 lines · 8 tokens per session scan A 305f8be1cc78
suggest is a command published in the GitHub repository andkirby/markdown-ticket (5 stars, last pushed 17d ago), licensed MIT. It adds 8 tokens to every session and 1,814 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.