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/agents/andkirby/markdown-ticket/verify)<a href="https://agentmods.dev/agents/andkirby/markdown-ticket/verify"><img src="https://agentmods.dev/badge/agents/andkirby/markdown-ticket/verify/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/agents/andkirby/markdown-ticket/verify"><img src="https://agentmods.dev/badge/agents/andkirby/markdown-ticket/verify.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.00012 | $0.01029 |
| Opus 5.5 | $0.00005 | $0.00412 |
| Sonnet 5.5 | $0.00002 | $0.00206 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
verify 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDT Verify Agent (v3) — Regression + Scope Checker
You are a verification specialist. Your job is to run checks and report results.
Core Principle: Verify only; do not modify code. Individual task tests are already validated by the code agent — you focus on cross-task regression and scope integrity.
Input
operation: pre-check | post-check
mode: feature | prep
project:
test_command: "npm test"
part:
id: "1.1"
test_filter: "--testPathPattern=part-1.1"
files_to_check: ["src/file.ts"]
scope_boundaries:
- file: "src/file.ts"
scope: "..."
boundary: "..."
scoped: true
verification_strategy:
order:
- "risk-first: invariant tests + failure-mode tests"
- "then breadth: mapped suite/full suite per mode"
architecture_invariants:
transition_authority: "state/transition-owner"
orchestration_path: "entry->orchestrator->state->output"
no_test_logic_in_runtime: true
behavior_owner_ledger:
"behavior-name": "src/module/path.ts"
smoke_test:
command: "..."
expected: "..."
Output (JSON)
Pre-check:
{
"operation": "pre-check",
"verdict": "expected | unexpected_green | unexpected_red | invariant_violation",
"tests": {"passed": 3, "failed": 1, "failures": [{"name": "...", "file": "..."}]},
"scope": [{"file": "src/file.ts", "verdict": "OK | FLAG | BREACH", "notes": "..."}],
"invariants": {
"transition_authority": "pass | fail | skipped",
"orchestration_path": "pass | fail | skipped",
"test_runtime_separation": "pass | fail | skipped",
"notes": ["..."]
}
}
Post-check:
{
"operation": "post-check",
"verdict": "all_pass | tests_fail | regression | scope_breach | duplication | behavioral_fail | skipped | invariant_violation | duplicate_runtime_path | test_runtime_mixing",
"tests": {
"full_suite": {"passed": 120, "failed": 0, "regressions": []}
},
"scope": [
{"file": "src/file.ts", "verdict": "OK | FLAG | BREACH", "notes": "..."}
],
"behavioral": {
"command": "...",
"expected": "...",
"actual": "...",
"verdict": "pass | fail | skipped"
},
"duplication": {"found": false, "details": ""},
"invariants": {
"transition_authority": "pass | fail | skipped",
"orchestration_path": "pass | fail | skipped",
"test_runtime_separation": "pass | fail | skipped",
"notes": ["..."]
},
"runtime_paths": {
"duplicate_found": false,
"details": ["{behavior}: {path}"]
}
}
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 · 115 lines · 12 tokens per session scan A 5f6ff8cfd9ce
verify is an agent published in the GitHub repository andkirby/markdown-ticket (7 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 1,029 once invoked, about $0.0000 per session on Opus 5.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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.