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/jonlwowski012/copilot-agent-factory/debug-test-failuresnpx skills add jonlwowski012/copilot-agent-factory --skill debug-test-failuresgit clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factoryWrote 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/jonlwowski012/copilot-agent-factory/debug-test-failures)<a href="https://agentmods.dev/skills/jonlwowski012/copilot-agent-factory/debug-test-failures"><img src="https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/debug-test-failures.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.01849 |
| Opus 5 | $0.00008 | $0.00924 |
| Sonnet 5 | $0.00003 | $0.00370 |
| Haiku 4.5 | $0.00002 | $0.00185 |
Grade A, and why
debug-test-failures 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.
How it starts
The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Debug Test Failures
When to Use This Skill
This skill activates when you need to:
- Investigate why tests are failing
- Debug specific test failures
- Understand test error messages
- Fix flaky or intermittent test failures
Prerequisites
This assumes tests are configured and running. Use run-tests skill to execute tests first.
Step-by-Step Workflow
Step 1: Run Tests and Identify Failures
Run tests with verbose output:
# Python
pytest -v
# JavaScript
npm test -- --verbose
# Go
go test -v ./...
Identify the failing test(s):
- Note the test file and function name
- Read the error message carefully
- Check the assertion that failed
Step 2: Run Only the Failing Test
Python (pytest):
pytest tests/test_file.py::test_function_name -v
JavaScript (Jest):
npm test -- tests/example.test.js -t "test name pattern"
Go:
go test -run TestFunctionName -v
Step 3: Add Debug Output
Python - Add print statements:
def test_example():
result = my_function(input_data)
print(f"DEBUG: result = {result}") # Debug output
print(f"DEBUG: type = {type(result)}")
assert result == expected
Run with output visible:
pytest -s tests/test_file.py::test_function_name
Python - Use pytest's debugging:
# Drop into debugger on failure
pytest --pdb
# Drop into debugger on first failure
pytest -x --pdb
JavaScript - Add console.log:
test('example', () => {
const result = myFunction(inputData);
console.log('DEBUG: result =', result);
expect(result).toBe(expected);
});
Step 4: Common Failure Patterns
AssertionError / Unexpected Value
Cause: Expected value doesn't match actual value
Debug steps:
- Print both expected and actual values
- Check data types match (string vs int, etc.)
- Check for whitespace, case sensitivity
- Verify test data setup
Example fix:
# Before - fails due to extra whitespace
assert result == "hello"
# After - strip whitespace
assert result.strip() == "hello"
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 · 322 lines · 16 tokens per session scan A 59345a5c0831
debug-test-failures is a skill published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 5d ago), licensed MIT. It adds 16 tokens to every session and 1,849 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…