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 skills/shenli/devtool-ax-kit/ax-failure-reportnpx skills add shenli/devtool-ax-kit --skill ax-failure-reportgit clone --depth 1 https://github.com/shenli/devtool-ax-kitWrote 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/skills/shenli/devtool-ax-kit/ax-failure-report)<a href="https://agentmods.dev/skills/shenli/devtool-ax-kit/ax-failure-report"><img src="https://agentmods.dev/badge/skills/shenli/devtool-ax-kit/ax-failure-report.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.00016 | $0.00127 |
| Opus 5 | $0.00008 | $0.00063 |
| Sonnet 5 | $0.00003 | $0.00025 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
ax-failure-report 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 5d 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.
What it actually says
Write a private, evidence-led report. State the repeated behavior before offering attribution. Include the exact protocol, fixture and verifier hashes, run IDs, repetition table, deterministic checks, safety boundary, limits, and a minimal regression candidate.
Ask the vendor to confirm the supported contract, review a reproduction, or provide a realistic regression case. Do not ask for agreement with a thesis. Share redacted evidence only: never attach credentials, raw secret-bearing trajectories, production data, or unbounded logs.
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.
- 5d ago First seen · 15 lines · 16 tokens per session scan A 8c14443930c5
ax-failure-report is a skill published in the GitHub repository shenli/devtool-ax-kit (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 16 tokens to every session and 127 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 skills, from other repositories
coder-agents-review
Use this skill when a repository already has an open pull request and you need to run the Coder Agents Review loop: request review with /coder-agents-review when needed, wait for feedback from the coder-agents-review GitHub app, fix issues, and repeat until the app comments approved.
write-docs
Authoring workflow and guardrails for writing, moving, or restructuring Coder documentation under docs/. Points at the canonical content guidelines and prose style guide, then walks research, routing, Diátaxis mode, structure, pedagogy, and validation. Counterpart to the doc-check skill, which reviews changes for…
dogfood
Run a Coder PR dogfood instance: inspect PR context, check out the right branch or stack, start Coder with scripts/develop.sh using agent-safe dev-instance practices, validate the changed functionality with UI evidence when needed, and report findings.
refine-plan
Iteratively refine development plans using TDD methodology. Ensures plans are clear, actionable, and include red-green-refactor cycles with proper test coverage.
pull-requests
Guide for creating, updating, and following up on pull requests in the Coder repository. Use when asked to open a PR, update a PR, rewrite a PR description, or follow up on CI/check failures.
pricing
Help the user decide what to charge and how to package it: the value metric, the tiers, the free-to-paid line, and finding the actual number. Use when the user is guessing at a price, priced too cheap and can't change it, is stuck on free vs paid, or believes "developers won't pay" so never charges.