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/ticket-creationgit 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/commands/andkirby/markdown-ticket/ticket-creation)<a href="https://agentmods.dev/commands/andkirby/markdown-ticket/ticket-creation"><img src="https://agentmods.dev/badge/commands/andkirby/markdown-ticket/ticket-creation.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01368 |
| Opus 5 | $0.00000 | $0.00684 |
| Sonnet 5 | $0.00000 | $0.00274 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
ticket-creation 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CR Creation Workflow (v9)
Pattern: Analyze context → Infer all parameters → Confirm/Refine → Execute
Core distinction: full mode = concrete artifacts (files, endpoints, methods); requirements mode = outcomes only (defer HOW to /mdt:architecture)
$ARGUMENTS
Use {TICKETS_PATH} from .mdt-config.toml for file paths.
{PROJECT_CODE} is provided by the hook (mdt-project-vars) and should be available in session context.
Parameter Schema
Infer ALL parameters from context before asking user:
| Parameter | Valid Values | Default Logic |
|---|---|---|
SPEC_MODE |
requirements, full |
requirements if vague/complex; full if specific files mentioned |
CR_TYPE |
Feature Enhancement, Bug Fix, Architecture, Technical Debt, Documentation, Research |
Infer from keywords (fix→Bug, add→Feature, refactor→Debt, investigate→Research) |
REQUIREMENTS_SCOPE |
full, brief, preservation, none |
See defaults table below |
MOTIVATION |
User requirement, Technical limitation, Bug/defect, Performance issue, Maintenance burden, Architectural gap |
Infer from context |
AREAS |
Infer from project structure (e.g., src/, lib/, tests/, api/) |
Scan top-level dirs + mentioned paths |
VERIFICATION |
Files exist, Tests pass, Endpoints work, Performance met, Manual, Docs updated |
Based on CR_TYPE |
REQUIREMENTS_SCOPE defaults:
| CR_TYPE | Default |
|---|---|
| Feature Enhancement | full |
| Bug Fix | brief |
| Architecture / Technical Debt / Documentation / Research | none |
Workflow
1. Analyze & Infer
Analyze user input, conversation history, and codebase context. Infer values for ALL parameters above.
For AREAS: List top-level directories in the project (e.g., ls -d */) and use actual folder names. Do NOT use generic terms like "Frontend/Backend/Shared" unless those folders exist.
2. Confirm Settings
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 · 122 lines · 0 tokens per session scan A 52194ea2a221
ticket-creation is a command published in the GitHub repository andkirby/markdown-ticket (5 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,368 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
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.