Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/patricio0312rev/skillsetnpx agentmods add skills/patricio0312rev/skillset/test-reporting-triage-skillWrote 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/patricio0312rev/skillset/test-reporting-triage-skill)<a href="https://agentmods.dev/skills/patricio0312rev/skillset/test-reporting-triage-skill"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skillset/test-reporting-triage-skill/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/patricio0312rev/skillset/test-reporting-triage-skill"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skillset/test-reporting-triage-skill.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.00054 | $0.03098 |
| Opus 5 | $0.00027 | $0.01549 |
| Sonnet 5 | $0.00011 | $0.00620 |
| Haiku 4.5 | $0.00005 | $0.00310 |
Grade A, and why
test-reporting-triage-skill 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.
This is a copy
100% identical to test-reporting-triage-skill — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Reporting & Triage Skill
Automatically triage test failures and suggest next actions.
Failure Categorization
// types/test-failure.ts
export type FailureCategory =
| "timeout"
| "assertion"
| "network"
| "database"
| "authentication"
| "permission"
| "configuration"
| "flaky"
| "infrastructure"
| "unknown";
export interface TestFailure {
testName: string;
category: FailureCategory;
errorMessage: string;
stackTrace: string;
suggestedOwner: string;
suggestedFixes: string[];
runId: string;
timestamp: Date;
}
Failure Analyzer
// analyzers/failure-analyzer.ts
export class FailureAnalyzer {
categorize(error: Error, testName: string): TestFailure {
const errorMessage = error.message.toLowerCase();
const stackTrace = error.stack || "";
// Timeout detection
if (errorMessage.includes("timeout") || errorMessage.includes("exceeded")) {
return {
testName,
category: "timeout",
errorMessage: error.message,
stackTrace,
suggestedOwner: "Performance Team",
suggestedFixes: [
"Check if API is slow",
"Increase timeout value",
"Optimize database query",
"Check for network issues",
],
runId: process.env.CI_RUN_ID || "local",
timestamp: new Date(),
};
}
// Network errors
if (
errorMessage.includes("econnrefused") ||
errorMessage.includes("network") ||
errorMessage.includes("fetch failed")
) {
return {
testName,
category: "network",
errorMessage: error.message,
stackTrace,
suggestedOwner: "DevOps Team",
suggestedFixes: [
"Check if service is running",
"Verify network connectivity",
"Check firewall rules",
"Verify DNS resolution",
],
runId: process.env.CI_RUN_ID || "local",
timestamp: new Date(),
};
}
// Database errors
if (
errorMessage.includes("database") ||
errorMessage.includes("prisma") ||
errorMessage.includes("unique constraint")
) {
return {
testName,
category: "database",
errorMessage: error.message,
stackTrace,
suggestedOwner: "Backend Team",
suggestedFixes: [
"Check database connection",
"Verify test data cleanup",
"Check for race conditions",
"Review migration status",
],
runId: process.env.CI_RUN_ID || "local",
timestamp: new Date(),
};
}
// Authentication errors
if (
errorMessage.includes("unauthorized") ||
errorMessage.includes("authentication") ||
errorMessage.includes("401")
) {
return {
testName,
category: "authentication",
errorMessage: error.message,
stackTrace,
suggestedOwner: "Auth Team",
suggestedFixes: [
"Check auth token validity",
"Verify test user credentials",
"Check session expiration",
"Review auth middleware",
],
runId: process.env.CI_RUN_ID || "local",
timestamp: new Date(),
};
}
// Assertion failures
if (
errorMessage.includes("expected") &&
errorMessage.includes("received")
) {
return {
testName,
category: "assertion",
errorMessage: error.message,
stackTrace,
suggestedOwner: this.determineOwnerFromPath(stackTrace),
suggestedFixes: [
"Review recent code changes",
"Check if test expectations are correct",
"Verify test data setup",
"Check for breaking changes",
],
runId: process.env.CI_RUN_ID || "local",
timestamp: new Date(),
};
}
// Default: unknown
return {
testName,
category: "unknown",
errorMessage: error.message,
stackTrace,
suggestedOwner: "On-Call Engineer",
suggestedFixes: [
"Review error message and stack trace",
"Check recent commits",
"Run test locally to reproduce",
"Add more specific error handling",
],
runId: process.env.CI_RUN_ID || "local",
timestamp: new Date(),
};
}
private determineOwnerFromPath(stackTrace: string): string {
if (stackTrace.includes("/frontend/")) return "Frontend Team";
if (stackTrace.includes("/backend/")) return "Backend Team";
if (stackTrace.includes("/api/")) return "API Team";
if (stackTrace.includes("/database/")) return "Database Team";
return "Development Team";
}
}
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 · 470 lines · 54 tokens per session scan A 031f92ce1ac2
test-reporting-triage-skill is a skill published in the GitHub repository patricio0312rev/skillset (6 stars, last pushed 8mo ago), licensed MIT. It adds 54 tokens to every session and 3,098 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to test-reporting-triage-skill, differing in 0 lines, and is treated as a copy.
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.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.