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/clarificationgit 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.00000 | $0.02778 |
| Opus 5 | $0.00000 | $0.01389 |
| Sonnet 5 | $0.00000 | $0.00556 |
| Haiku 4.5 | $0.00000 | $0.00278 |
Grade A, and why
clarification 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 2d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDT Ticket Clarification Workflow (v2)
Interactive clarification workflow for MDT architectural decision records (ADRs) using MCP mdt-all ticket system. Identifies underspecified areas in CR tickets and encodes answers directly into the ticket content.
Core Principle: Ensure concrete artifact specifications exist before implementation. Every ambiguity must be resolved with specific file/component/endpoint references, not behavioral descriptions.
User Input
$ARGUMENTS
Session Context
Use {TICKETS_PATH} in all file path templates below (if it's not defined read ticketsPath key from .mdt-config.toml).
You MUST consider the user input before proceeding (if not empty).
Outline
Goal: Detect and reduce ambiguity or missing artifact specifications in the active CR ticket using an interactive questioning interface and record clarifications directly in the ticket.
Note: This clarification workflow should run BEFORE detailed implementation planning. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.
Execution steps:
-
Load the CR ticket using
mdt-all:get_crwith mode="full" to retrieve both attributes and markdown content.- Parse CR key, project code, current status from response
- If ticket doesn't exist, abort and instruct user to create CR first
- If ticket status is "Implemented" or "Rejected", warn that clarification may not be appropriate
-
Perform structured artifact-specification scan using this taxonomy. For each category, mark status: Clear / Partial / Missing. Produce internal coverage map for prioritization (do not output raw map unless no questions will be asked).
Artifact Identification:
- Files, components, modules explicitly named
- Endpoints/APIs with concrete paths
- Methods/functions with signatures
- Configuration files and their structure
- Database entities and schema elements
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.
- 2d ago First seen · 273 lines · 0 tokens per session scan A a76b3e715132
clarification is a command published in the GitHub repository andkirby/markdown-ticket (5 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,778 tokens. 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.