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/requirementsgit 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/requirements)<a href="https://agentmods.dev/commands/andkirby/markdown-ticket/requirements"><img src="https://agentmods.dev/badge/commands/andkirby/markdown-ticket/requirements.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.02676 |
| Opus 5 | $0.00000 | $0.01338 |
| Sonnet 5 | $0.00000 | $0.00535 |
| Haiku 4.5 | $0.00000 | $0.00268 |
Grade A, and why
requirements 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDT Requirements Specification Workflow (v5)
Generate behavioral requirements from CR. Output: {TICKETS_PATH}/{CR-KEY}/requirements.md
Core Principle: Requirements describe WHAT the system does. Architecture decides WHERE and HOW.
Skill Discovery
Check AGENTS.md for skills matching this workflow. If found, invoke via Skill tool before proceeding.
User Input
$ARGUMENTS
Session Context
Use {TICKETS_PATH} from .mdt-config.toml.
When to Use (and When to Skip)
| CR Type | Generate? | Why |
|---|---|---|
| Feature Enhancement | Yes | New behaviors need specification |
| Complex Bug Fix | Yes (brief) | Multiple behaviors affected |
| Simple Bug Fix | Skip | CR acceptance criteria suffices |
| Refactoring | Skip | No new behavior → /mdt:architecture |
| Tech Debt | Skip | Structure change → /mdt:architecture |
| Documentation | Skip | No behavioral requirements |
Quick test: If CR has <3 distinct behaviors, skip requirements.md unless the CR explicitly sets Requirements Scope.
Carryover rule: Any constraints or edge-case rules in requirements must be carried into architecture and tasks (by ID).
Deviation rule: If architecture proposes a simpler alternative that changes a stated requirement, mark it as Decision Needed and do not change the requirement until explicitly approved.
Security rule: If requirements involve executing external commands or substituting user content (e.g., {text} placeholders), include a security constraint for escaping/command injection prevention and carry it forward to tests.
Traceability rule: /mdt:bdd must not introduce behaviors that are not in requirements. If a needed behavior is missing, add it here or flag for /mdt:clarification before writing BDD.
EARS Syntax (Quick Reference)
| Type | Template | Example |
|---|---|---|
| Event | WHEN <trigger>, the system shall <action> |
WHEN user clicks Save, the system shall persist within 200ms |
| State | WHILE <state>, the system shall <action> |
WHILE offline, the system shall queue mutations |
| Error | IF <condition>, THEN the system shall <action> |
IF validation fails, THEN the system shall show field errors |
| Always | The system shall <action> |
The system shall hash passwords with bcrypt |
| Absence | WHILE <dependency> is unavailable, the system shall <fallback> |
WHILE external detection is unavailable, the system shall proceed without applying a constraint |
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 · 294 lines · 0 tokens per session scan A 56884ea3b5be
requirements is a command published in the GitHub repository andkirby/markdown-ticket (5 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,676 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.