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/domain-lens)<a href="https://agentmods.dev/commands/andkirby/markdown-ticket/domain-lens"><img src="https://agentmods.dev/badge/commands/andkirby/markdown-ticket/domain-lens.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.1 | $0.00000 | $0.03044 |
| Opus 5 | $0.00000 | $0.01522 |
| Sonnet 5 | $0.00000 | $0.00609 |
| Haiku 4.5 | $0.00000 | $0.00304 |
Grade A, and why
domain-lens 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 7d 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 — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDT Domain Lens (v3)
Surface strategic DDD constraints before architectural decisions. Output is intentionally minimal — principles only, not prescriptions.
Core Principle: Identify domain boundaries and invariants that should constrain structural decisions downstream. All analysis MUST be grounded in actual codebase — no invented code terms.
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).
Output
Creates {TICKETS_PATH}/{CR-KEY}/domain.md (concise)
When to Use
| CR Type | Use Domain Lens? |
|---|---|
| New feature with business logic | ✅ Yes |
| Complex integration across modules | ✅ Yes |
| Domain model changes | ✅ Yes |
| Simple CRUD | ❌ Skip |
| Refactoring / Tech-debt | ❌ Use /mdt:domain-audit instead |
| Infrastructure / Config | ❌ Skip |
| Bug fix | ❌ Skip |
What This Is NOT
- ❌ Class/file structure recommendations (architecture's job)
- ❌ Verbose domain model documentation
- ❌ Pattern prescriptions ("use repository pattern")
- ❌ Implementation guidance
- ❌ Invented code terms from CR descriptions
Execution Steps
Step 1: Load Context
mdt-all:get_crwithmode="full"— abort if CR doesn't exist- Load
{TICKETS_PATH}/{CR-KEY}/requirements.mdif exists - Extract list of affected artifacts from CR
Step 2: Ground in Codebase
Critical: All domain analysis MUST be grounded in actual code.
If CR lists affected artifacts:
- Read each artifact file
- Extract actual class/interface/type names
- Note actual structure and relationships
- Build vocabulary of real code terms
Grounding Rules:
- "Code Term" column MUST use actual identifiers from codebase
- If concept is new (no code exists yet), mark as
(new) - Do NOT invent code terms from CR descriptions
- If CR describes something like "Three-Strategy Configuration", search for actual implementation before mapping
- If unsure whether code exists, search codebase before claiming
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.
- 7d ago First seen · 409 lines · 0 tokens per session scan A 60c0a6bee277
domain-lens is a command published in the GitHub repository andkirby/markdown-ticket (5 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,044 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.