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/commands/andkirby/markdown-ticket/reflection)<a href="https://agentmods.dev/commands/andkirby/markdown-ticket/reflection"><img src="https://agentmods.dev/badge/commands/andkirby/markdown-ticket/reflection/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/commands/andkirby/markdown-ticket/reflection"><img src="https://agentmods.dev/badge/commands/andkirby/markdown-ticket/reflection.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.02196 |
| Opus 5.5 | $0.00000 | $0.00878 |
| Sonnet 5.5 | $0.00000 | $0.00439 |
| Haiku 4.5 | $0.00000 | $0.00220 |
Grade A, and why
reflection 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.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDT Ticket Reflection Workflow (v4)
Capture post-implementation learnings from the conversation and selected workflow artifacts, then encode approved updates into the CR and any chosen MDT documents. Focus on artifact-level insights and specification adjustments only.
Core Principle: Reflection starts from the documents that shaped the work. Ask which workflow documents should be read, recommend which of them should be updated based on the changes that were actually made, then record approved updates with concrete artifact references.
User Input
$ARGUMENTS
Session Context
Use {TICKETS_PATH} in all file path templates below (if it's not defined read ticketsPath from .mdt-config.toml).
You MUST consider the user input before proceeding.
Source Ownership
Use this routing table when recommending update targets:
| Change Type | Update Target |
|---|---|
| Implemented behavior, constraints, acceptance semantics | requirements.md |
| Structure, ownership, integrations, runtime flow, prerequisites | architecture.md |
| Verification intent, required checks, regression coverage | tests.md |
| Unresolved issues, compromises, follow-up cleanup | debt.md |
| Session summary, links, user-approved notes | CR Section 8 (Clarifications) |
| Context note with no source document change | CR only |
Execution Steps
-
Load CR Context
Use
mdt-all:get_crwithmode="full":- Parse CR key, project code, and current status
- If the ticket doesn't exist, abort and instruct the user to create the CR first
- If the status is
Rejected, warn that reflection may not be appropriate - If the status is not
Implemented, confirm the user wants to reflect on in-progress work
-
Select Documents to Review
Detect which of these documents exist under
{TICKETS_PATH}/{CR-KEY}/:requirements.mdbdd.mdarchitecture.mdtests.mdtasks.mddebt.mdpoc.mddomain.mddomain-audit.mdprep/architecture.md,prep/tests.md,prep/tasks.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.
- 1mo ago First seen · 272 lines · 0 tokens per session scan A 69f52b558eb0
reflection is a command published in the GitHub repository andkirby/markdown-ticket (7 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,196 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.