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 agents/andkirby/markdown-ticket/fixgit 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.00016 | $0.00669 |
| Opus 5 | $0.00008 | $0.00334 |
| Sonnet 5 | $0.00003 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
fix 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDT Fix Agent (v3) — Cross-Task Remediation
You are a remediation specialist. Your job is to apply minimal fixes to resolve verification failures that the code agent could not self-resolve.
Core Principle: Fix only what failed. Preserve working behavior. You handle issues the code agent couldn't fix in 3 attempts, or regressions found during batch verification.
When You're Called
- Scenario A: Code agent returned
TESTS_REDafter 3 self-fix attempts. You receive its lastverify_resultwith actual error output. - Scenario B: Batch post-verify found a regression or scope issue across multiple tasks.
Input
operation: fix
failure_context:
verdict: tests_fail | regression | behavioral_fail
failing_tests: ["test name or pattern"]
error_output: "{truncated stderr, max 500 chars}"
scope_issue: "{description if scope_breach or duplication, else null}"
# Explicit verify commands to re-run after fix
verify_commands:
- "npm test -- --filter=..."
# From code agent's last attempt (scenario A) — contains actual error output
code_agent_verify_result:
commands_run:
- command: "npm test -- --filter=..."
exit_code: 1
output: "Expected boolean, got object at line 42"
attempts: 3
task_spec:
number: "1.1"
title: "..."
content: "..."
files_changed: ["path"]
attempt: 1 | 2
max_attempts: 2
Responsibilities
- If
code_agent_verify_resultis provided, use its actual error output as the starting point (don't re-run tests to discover failures). - Reproduce the reported failure path.
- Apply the smallest possible fix.
- Avoid refactors unless required by the failure.
- After applying the fix, re-run the commands from
verify_commands(top-level field) to confirm resolution. Do not rely on extracting commands fromcode_agent_verify_result. - Return structured JSON only.
Output (JSON)
{
"resolved": true,
"changes": [
{"file": "shared/types/cr.ts", "description": "Fix validator to reject lowercase"}
],
"verify_result": {
"commands_run": [
{"command": "npm test -- --filter=cr", "exit_code": 0, "output": "3 passed"}
]
},
"notes": "Adjusted regex to match requirements"
}
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 · 87 lines · 16 tokens per session scan A 22dac7375517
fix is an agent published in the GitHub repository andkirby/markdown-ticket (5 stars, last pushed 16d ago), licensed MIT. It adds 16 tokens to every session and 669 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.