ZeroClaw is a Rust-based runtime for running a personal AI assistant on a user's own machine, with connections to language-model providers, communication channels, and external tools. It is for people who want to operate an assistant across channels such as Discord, Telegram, email, voice, webhooks, or a command line while keeping control of its data and credentials. The catalogue add-ons provide workflows and agents for using ZeroClaw.
Borrowing it
Nothing to install: this file belongs to zeroclaw-labs/zeroclaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zeroclaw-labs/zeroclaw/master/.claude/skills/github-issue-triage/SKILL.mdgit clone --depth 1 https://github.com/zeroclaw-labs/zeroclawWrote 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/zeroclaw-labs/zeroclaw/github-issue-triage)<a href="https://agentmods.dev/skills/zeroclaw-labs/zeroclaw/github-issue-triage"><img src="https://agentmods.dev/badge/skills/zeroclaw-labs/zeroclaw/github-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/zeroclaw-labs/zeroclaw/github-issue-triage"><img src="https://agentmods.dev/badge/skills/zeroclaw-labs/zeroclaw/github-issue-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector pass
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.00140 | $0.02029 |
| Opus 5.5 | $0.00056 | $0.00812 |
| Sonnet 5.5 | $0.00028 | $0.00406 |
| Haiku 4.5 | $0.00014 | $0.00203 |
Grade A, and why
github-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 2mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ZeroClaw Issue Triage Agent
You are an autonomous issue triage and lifecycle agent for ZeroClaw. You triage, label, link, close, and maintain the health of the issue backlog — acting within defined authority bounds and escalating any ambiguity to the user before acting.
Before You Start
Read these repository files at the start of every session — they are authoritative and override this skill if conflicts exist:
AGENTS.md— conventions, risk tiers, anti-patterns, core engineering constraintsdocs/book/src/maintainers/reviewer-playbook.md— Issue Triage sectiondocs/book/src/maintainers/pr-workflow.md— Review SLA and queue disciplinedocs/book/src/contributing/privacy.md— privacy rules, neutral wording requirements
Then read references/triage-protocol.md for the full mode-by-mode workflow.
The protocol encodes operational details rooted in RFC #5577 (governance), RFC #5615 (contribution culture), and later maintainer policy corrections. docs/book/src/maintainers/labels.md#issue-stale-policy is the sole operational source for current stale timing, qualifying activity, exclusions, and re-engagement. The protocol explains how to apply that policy; FND-003 and issue #5577 preserve governance intent and decision history.
Invocation
/github-issue-triage → accounting: show backlog state, prompt for mode
/github-issue-triage 123 → triage a single issue by number
/github-issue-triage <url> → triage a single issue by URL
/github-issue-triage triage → process new/untriaged issues
/github-issue-triage sweep → full backlog sweep
/github-issue-triage stale → maintainer stale-policy enforcement pass
/github-issue-triage wont-fix → architectural won't-fix pass
No args: Run the accounting pass from references/triage-protocol.md §1. Show current backlog state and prompt the user to choose a mode. Do not begin any triage action until the user selects one.
Quick Reference: Modes
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.
- 2mo ago First seen · 127 lines · 140 tokens per session scan A ac94519d51b3
github-issue-triage is a skill published in the GitHub repository zeroclaw-labs/zeroclaw (33,061 stars, last pushed yesterday), licensed Apache-2.0. It adds 140 tokens to every session and 2,029 once invoked, about $0.0006 per session on Opus 5.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
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.
github-issues
Create, triage, label, assign GitHub issues via gh or REST.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.