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 zaks-io/skills --skill ziw-triagegit clone --depth 1 https://github.com/zaks-io/skillsWrote 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/zaks-io/skills/ziw-triage)<a href="https://agentmods.dev/skills/zaks-io/skills/ziw-triage"><img src="https://agentmods.dev/badge/skills/zaks-io/skills/ziw-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/zaks-io/skills/ziw-triage"><img src="https://agentmods.dev/badge/skills/zaks-io/skills/ziw-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.00064 | $0.04713 |
| Opus 5 | $0.00032 | $0.02357 |
| Sonnet 5 | $0.00013 | $0.00943 |
| Haiku 4.5 | $0.00006 | $0.00471 |
Grade A, and why
ziw-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 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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage
Issue Triage manages the issue tracker backlog so Orchestrator can run. It turns tracker items into well-shaped, dependency-aware, agent-ready work or explicit human/To Issues follow-up.
The end state is a useful Todo backlog:
- every
Todoimplementation ticket is a one-PRkind-slice - ready work has
ready-for-agent, the configured route, required labels, required estimate, complete body contract, and predicted footprint - blocked ready work stays in
Todowith blocker relationships encoded - not-ready work is labeled or moved to the configured human, intake, parked, or To Issues path when config grants that authority
- Orchestrator can consume the final
starts, blocked-ready list, and next actions without re-triaging the same queue
Default triage starts from the configured ready and intake states, configured
active or PR-linked issues that need reconciliation, and direct blockers of those
tickets. In most Linear repos this means Todo, Triage, active or PR-linked
issues with stale workflow metadata, and any active issues that directly block
those tickets. Do not include unrelated Linear Backlog, Duplicate, Done,
canceled, icebox, or other parked/terminal states by default.
This skill is script-driven tracker grooming. It is not research, implementation, code review, repo health monitoring, CI diagnosis, deploy diagnosis, security scanning, or production triage.
Read only:
docs/agents/workflow/config.md- source-of-truth specs, roadmap, milestone, and project docs cited by the config or scoped tickets
- issue tracker metadata, bodies, comments, labels, statuses, estimates, projects, parents, and relationships
- explicit user instructions
- approved workflow script outputs from
skills/ziw-orchestrate/scripts
Run the scripts, read the output, inspect only the bounded tracker scope and its
cited source-of-truth docs, then fix the tickets. The scripts are the observation
layer for queue, PR, and worker state; the agent does not rediscover that state
manually. No manual code search, implementation file reads, one-off gh
queries, CI spelunking, deploy checks, log review, security tool runs, or broad
repo health checks. If handoff quality depends on information that is not in the
tracker, config, cited source-of-truth docs, or script output, leave the exact
missing field for To Issues or a human.
Tracker/MCP tools are for applying ticket mutations and reading specific ticket fields that the scripts do not return. Do not use MCP calls to rebuild the same inventory, PR state, dependency frontier, or readiness decisions that the scripts already compute.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +24 lines c5b6c0d9a761
- 11d ago First seen · 406 lines · 64 tokens per session scan A 6d985ea77ea7
ziw-triage is a skill published in the GitHub repository zaks-io/skills (3 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 4,713 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 skills, from other repositories
jira-issue-create
Create one or more Jira issues through acli from user-approved drafts using heading-based Context, Acceptance criteria, and Engineering notes sections. Use only when explicitly invoked to create Jira issues; use jira-issue-refine when requirements still need refinement.
jira-issue-deliver
Autonomously deliver one Jira issue from intake to a ready GitHub pull request. Use only when the user authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback.
roadmap-task-deliver
Deliver the first eligible unfinished roadmap task through implementation, review, green CI, PR merge, and a task-status update. Use for autonomous delivery from local roadmap and task files. Files can be outside the code repository or outside Git.
jira-issue-refine
Refine one draft or existing Jira issue into a clear, evidence-backed, bounded delivery contract without implementing it. Use when creating or revising an issue before engineering handoff, especially when behavior, repository ownership, acceptance evidence, dependencies, risk, environment needs, or scope remain…
ai-maintainer-copilot
Use when maintaining open-source projects with AI assistance: issue triage, pull request review, release notes, maintainer automation, Codex for OSS application evidence, and privacy or safety guardrails for AI-assisted workflows.
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.