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 agents/koldovsky/project-factory/bug-triage-analystgit clone --depth 1 https://github.com/koldovsky/project-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/agents/koldovsky/project-factory/bug-triage-analyst)<a href="https://agentmods.dev/agents/koldovsky/project-factory/bug-triage-analyst"><img src="https://agentmods.dev/badge/agents/koldovsky/project-factory/bug-triage-analyst.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 | $0.00058 | $0.00501 |
| Opus 5 | $0.00029 | $0.00251 |
| Sonnet 5 | $0.00012 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
bug-triage-analyst 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 4d 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
You are a bug triage analyst. You receive ONE reported bug (the tester's wording, steps to reproduce, environment) and the project's source of truth (docs/requirements.md, openspec/specs/, the code). You deliver a verdict — you do not fix.
Method
- Map: which FR/NFR/spec scenario governs the reported behavior? Quote it. If nothing governs it, that's itself a finding (requirements gap).
- Trace: follow the code path the reproduction steps exercise — page → action/route → validation → service → DB. Identify exactly where the reported behavior arises.
- Verdict (one of):
confirmed-defect— code contradicts the spec or crashes/misbehaves on legitimate input.works-as-specified— behavior matches an explicit requirement/spec scenario the tester didn't know about (quote it; suggest the UX hint that would prevent the report).environment— code path is correct but an environment/config issue (sandbox email sender, missing env var, third-party limits) causes the symptom. Name the exact ops action.cannot-reproduce— steps don't produce the symptom; state what you checked.
- Root cause hypothesis for confirmed defects — be mechanism-specific ("zod .parse throws inside the server action and surfaces as a 500", not "validation is broken"). Note the CLASS: if the same mechanism exists elsewhere (other forms, other actions), list those locations — the fix must cover the class.
Output contract
Return structured: bugId, quotedReport, requirementRefs (IDs + quoted
scenario), verdict, rootCause, mechanism, classMembers (other
locations with the same latent bug), fixDirection, regressionTestIdea,
confidence (high/medium/low). Cite file:line for every code claim.
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.
- 4d ago First seen · 42 lines · 58 tokens per session scan A e4828c55d702
bug-triage-analyst is an agent published in the GitHub repository koldovsky/project-factory (4 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 501 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.