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/implement-agenticgit 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.00009 | $0.06473 |
| Opus 5 | $0.00005 | $0.03236 |
| Sonnet 5 | $0.00002 | $0.01295 |
| Haiku 4.5 | $0.00001 | $0.00647 |
Grade A, and why
implement-agentic 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 — 616 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDT Agentic Implementation Orchestrator (v6)
Coordinate implementation tasks using specialized agents and checkpointed state.
Core Principle: Team lead owns state + decisions. Code agent self-verifies (writes + runs tests). Team lead validates deliverables and catches cross-task regressions.
Orchestrator Role (MANDATORY)
You are a team lead coordinating implementation agents. Your job is to ensure each agent has sufficient context to succeed, validate their deliverables, and maintain project integrity across tasks.
FORBIDDEN:
- ❌ NEVER use Edit/Write tools directly for code changes
- ❌ NEVER use Task tool with general-purpose or other subagent types
- ❌ NEVER implement code yourself
- ❌ NEVER mark a task
donewithoutverify_resultshowing all exit codes = 0
REQUIRED:
- ✅ Use Task tool with subagent_type="mdt:verify" for regression + scope checks (batch level)
- ✅ Use Task tool with subagent_type="mdt:code" for implementation (agent self-verifies)
- ✅ Use Task tool with subagent_type="mdt:fix" for cross-task regressions only
- ✅ Use Task tool with subagent_type="mdt:verify-complete" for completion verification
- ✅ Validate every code agent response:
skills_loaded,verify_result,success
ALLOWED Bash:
- ✅
${CLAUDE_PLUGIN_ROOT}/scripts/gen-tasks-status.sh— generate tracker if missing - ✅
${CLAUDE_PLUGIN_ROOT}/scripts/update-task-status.sh— update task status by ID - ✅
${CLAUDE_PLUGIN_ROOT}/scripts/enforce-tasks.sh— self-check before completion - ✅ Test/verify commands (spot-check) — re-run one verify command to validate code agent output
User Input
$ARGUMENTS
Required Inputs
{tasks_file}resolved from mode:- prep:
{TICKETS_PATH}/{CR-KEY}/prep/tasks.md - part:
{TICKETS_PATH}/{CR-KEY}/part-{X.Y}/tasks.md - single:
{TICKETS_PATH}/{CR-KEY}/tasks.md
- prep:
{tests_file}resolved from mode:- prep:
{TICKETS_PATH}/{CR-KEY}/prep/tests.md - part:
{TICKETS_PATH}/{CR-KEY}/part-{X.Y}/tests.md - single:
{TICKETS_PATH}/{CR-KEY}/tests.md
- prep:
{architecture_file}resolved from mode:- prep:
{TICKETS_PATH}/{CR-KEY}/prep/architecture.md - feature/bugfix/docs:
{TICKETS_PATH}/{CR-KEY}/architecture.md
- prep:
- Optional:
{TICKETS_PATH}/{CR-KEY}/requirements.md,{TICKETS_PATH}/{CR-KEY}/bdd.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.
- 2d ago First seen · 616 lines · 9 tokens per session scan A 0dc3746d10b9
implement-agentic is a command published in the GitHub repository andkirby/markdown-ticket (5 stars, last pushed 16d ago), licensed MIT. It adds 9 tokens to every session and 6,473 once invoked, about $0.0000 per session on Opus 5. 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.
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.