What is file-test-bug?

A workflow for reporting failed local integration tests as GitHub issues. Integration tests check whether multiple parts of a system work together.

Use it after an integration test fails to inspect JUnit results, identify whether the skill, test, or model caused the problem, and create an issue in the specified GitHub repository.

It records test failures with their logs, expected behavior, diagnosis, and suggested fixes so they can be investigated consistently.

file-test-bug — Skill for Claude Code by Tyler-R-Kendrick

Install

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.

Any agent

npx skills add Tyler-R-Kendrick/agent-skills --skill file-test-bug

Clone the repo

git clone --depth 1 https://github.com/Tyler-R-Kendrick/agent-skills

Made for: Claude Code.

Or install agent-skills, the plugin that ships this one along with the rest of its 57 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/file-test-bug/github.svg)](https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/file-test-bug)

Your own site

<a href="https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/file-test-bug"><img src="https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/file-test-bug/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/file-test-bug"><img src="https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/file-test-bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 606 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00044	$0.00606
Opus 5	$0.00022	$0.00303
Sonnet 5	$0.00009	$0.00121
Haiku 4.5	$0.00004	$0.00061

Measured 11d ago against content hash bb4f6217d137, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

file-test-bug 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 11d 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.

.agent/skills/file-test-bug/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

File Test Bug

Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures.

Input

Skill name (required): e.g., azure-role-selector, appinsights-instrumentation
Test run (optional): Timestamp of test run. Defaults to most recent with logs for the skill.

Steps

Ask user for skill name if not provided
Parse tests/reports/junit.xml for failures matching the skill
Find test run directory (specified or most recent with matching logs)
Read agent-metadata.md from tests/reports/test-run-<timestamp>/<skillname>-<testname>/
For each failure, read the actual line of code from the test file using the location (file:line) from junit.xml
REQUIRED - Write diagnosis BEFORE creating issue:
- Analyze the agent-metadata.md to understand what the agent did
- Compare agent behavior to what the test expected (from the assertion)
- Identify the root cause (skill issue, test issue, or model behavior)
- Write 2-3 sentences per failed test explaining WHY it failed
- Suggest potential fixes (update skill, update test, or update fixtures)
Create issue via github-mcp-server-create_issue:

owner: microsoft
repo: github-copilot-for-azure
title: Integration test failure in <skill-name>
labels: ["bug", "integration-test"]
body: |
  ## Failed Tests
  - <test-name>: <error message>
  
  ## Diagnosis
  
  ### Root Cause
  <1-2 sentences explaining WHY the test failed based on agent-metadata.md analysis>
  
  ### Analysis per Test
  - **<test-name>**: <what agent did vs what test expected>
  
  ### Suggested Fix
  <one of: update skill, update test assertions, provide test fixtures>

  ## Details
  ### <test-name>
  **Error:** <failure from junit.xml>
  **Location:** <file:line>
  ```typescript
  <actual line of code from the test file at the specified line number>

Read the full file on GitHub · 69 lines

Changes

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.

11d ago First seen · 69 lines · 44 tokens per session scan A bb4f6217d137

Subscribe to this mod's changes

file-test-bug is a skill published in the GitHub repository Tyler-R-Kendrick/agent-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 606 once invoked, about $0.0002 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

file-test-bug