Borrowing it
Nothing to install: this file belongs to testdino-hq/testdino-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/testdino-hq/testdino-mcp/main/.claude/skills/fix/SKILL.mdgit clone --depth 1 https://github.com/testdino-hq/testdino-mcpWrote 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/testdino-hq/testdino-mcp/fix)<a href="https://agentmods.dev/skills/testdino-hq/testdino-mcp/fix"><img src="https://agentmods.dev/badge/skills/testdino-hq/testdino-mcp/fix/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/skills/testdino-hq/testdino-mcp/fix"><img src="https://agentmods.dev/badge/skills/testdino-hq/testdino-mcp/fix.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.00023 | $0.00692 |
| Opus 5 | $0.00012 | $0.00346 |
| Sonnet 5 | $0.00005 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
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 9d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix the bug: $ARGUMENTS
Workflow
0. Check Tracking + Memory
- Check auto-memory for prior lessons matching this bug type
- Read
ISSUES.md— find the relevant tracked issue by ID or description - If the issue isn't tracked yet, add it to
ISSUES.mdfirst (assign next ISS-NNN ID) - Update issue status to
IN PROGRESS
1. Verify the Issue Exists
- Read the code at the reported location
- Confirm the bug is real, not a false alarm
- If already fixed or no longer applies: update
ISSUES.mdstatus toFIXEDand stop
2. Root-Cause Analysis
- Read the code — understand what it does, not what you think it does
- Trace the data flow — for tool issues: schema → handler → endpoint → request → response
- Never stop at the first failure — ask "why did THIS fail?" and trace backward
- Check Known Patterns & Pitfalls in CLAUDE.md — is this a known pattern?
3. Implement the Fix
- Fix the root cause — not the symptom
- Minimal change — don't refactor surrounding code
- Follow the project's conventions (CLAUDE.md)
- If the fix changes tool behavior or params, note what docs need updating
4. Test
- Can an existing test be updated to cover the fix? Update it
- Does the fix change observable behavior no test covers? Add a regression test
- The test must fail before the fix and pass after — verify this mentally or actually
5. Verify
Run the quality gate immediately after the fix:
npm run typecheck && npm run lint && npm run test -- --passWithNoTests
All must pass. git diff — confirm only intentional changes.
6. Document
This step is not optional. The fix is incomplete until:
ISSUES.mdis updated with:- Status:
FIXEDwith date - Root cause (file:line — one sentence)
- Fix description
- Files changed
- Tests added/updated
- Status:
docs/TOOLS.mdupdated if the fix changes tool behaviorCLAUDE.mdKnown Patterns & Pitfalls updated if the pattern is generalizable- Auto-memory lesson written if anything went wrong during the fix process
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.
- 9d ago First seen · 86 lines · 23 tokens per session scan A 0703b84e88a9
fix is a skill published in the GitHub repository testdino-hq/testdino-mcp (9 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 692 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
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.