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 skills add saemihemma/lead-producer-oss --skill workflow-issue-triagegit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/workflow-issue-triage)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/workflow-issue-triage"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-issue-triage/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/saemihemma/lead-producer-oss/workflow-issue-triage"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-issue-triage.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.00048 | $0.00531 |
| Opus 5 | $0.00024 | $0.00266 |
| Sonnet 5 | $0.00010 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
workflow-issue-triage 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 12d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage Workflow
Purpose
Packaging and handoff layer for debugging work. Turns findings from prior investigation into a durable local artifact with clear next steps and ownership.
Use When
- Investigation findings need a durable local artifact
- Clean handoff is needed after
workflow-systematic-debugging, Dev Team, QA, or manual investigation - Reproduction notes, root-cause summary, acceptance criteria, and fix slices should live in one place
- Task spans investigation now and implementation later
Do NOT Use When
- Root cause is still unknown and the next step is investigation (use
workflow-systematic-debugging) - Issue is already understood and user wants direct implementation
- Task is feature request, not bug
Default Artifact
Persist to _artifacts/triage-<slug>.md:
- Problem
- Reproduction
- Root Cause Summary
- TDD Fix Plan
- Acceptance Criteria
- Open Questions / Unknowns
Packaging Workflow
- Capture the best investigation evidence available.
- Record tightest reliable reproduction.
- State confirmed root cause plainly; if still unconfirmed, label the current best hypothesis and confidence.
- Package next fix steps as small TDD-oriented slices.
- Assign likely follow-up owner.
- Record what remains unknown.
TDD Fix Plan
Each slice should answer:
- What failing behavior to capture first?
- Smallest implementation change to make test pass?
- Cleanup or refactor that waits until slice is green?
Anti-Patterns
- Behavior-level explanations, not file-by-file edit lists.
- Name root cause plainly; rank multiple candidates by confidence.
- Make acceptance criteria observable and testable.
Output Discipline
- Follow the Default Output structure as both minimum and maximum. Do not add extra sections.
- Keep findings concise: 2-5 points per section.
Anti-Drift Rules
- This workflow packages investigation results. It does not perform root-cause debugging.
- If
_artifacts/directory does not exist, ask the user where to save artifacts. - If the next best step is still root-cause investigation, route to
workflow-systematic-debugginginstead of guessing. - Name root cause plainly. Do not hide uncertainty behind confident language.
- Make acceptance criteria observable and testable, not vague.
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.
- 12d ago First seen · 59 lines · 48 tokens per session scan A f90b39153a44
workflow-issue-triage is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 8d ago), licensed MIT. It adds 48 tokens to every session and 531 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.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
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.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
test-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.