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 poindexter12/waypoint --skill gh-issue-triagegit clone --depth 1 https://github.com/poindexter12/waypointWrote 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/poindexter12/waypoint/gh-issue-triage)<a href="https://agentmods.dev/skills/poindexter12/waypoint/gh-issue-triage"><img src="https://agentmods.dev/badge/skills/poindexter12/waypoint/gh-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/poindexter12/waypoint/gh-issue-triage"><img src="https://agentmods.dev/badge/skills/poindexter12/waypoint/gh-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.00060 | $0.01332 |
| Opus 5 | $0.00030 | $0.00666 |
| Sonnet 5 | $0.00012 | $0.00266 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
gh-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 11d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage
Rules and workflows for categorizing, labeling, and prioritizing GitHub issues.
Quick Reference
| Label Type | Purpose | Mutually Exclusive? |
|---|---|---|
| Type | What kind of issue | Yes |
| Priority | How urgent | Yes |
| Status | Current state | Yes |
| Area | Which component | No |
Label Taxonomy
Type Labels (mutually exclusive)
| Label | Description | Color |
|---|---|---|
bug |
Something is broken | #d73a4a (red) |
feature |
New functionality | #a2eeef (cyan) |
enhancement |
Improvement to existing feature | #84b6eb (blue) |
docs |
Documentation only | #0075ca (dark blue) |
chore |
Maintenance, deps, infra | #fef2c0 (yellow) |
Priority Labels (mutually exclusive)
| Label | Description | Response |
|---|---|---|
priority: critical |
Drop everything, fix now | Immediate |
priority: high |
Next up after current work | This sprint |
priority: medium |
Normal backlog | Scheduled |
priority: low |
Nice to have, someday | Backlog |
Status Labels (mutually exclusive)
| Label | Description |
|---|---|
needs-triage |
New, not yet categorized |
needs-info |
Waiting for reporter clarification |
accepted |
Triaged and in backlog |
in-progress |
Someone is working on it |
blocked |
Can't proceed, waiting on something |
Area Labels (project-specific, not exclusive)
Define based on your project structure:
area: apiarea: cliarea: docsarea: uiarea: auth
Triage Workflow
Step 1: New Issues
Every new issue gets needs-triage label automatically (via GitHub Actions or manually).
Step 2: Initial Review
Is this a duplicate?
YES → Close with "Duplicate of #N", link original
NO → Continue
Is this spam/invalid?
YES → Close without label
NO → Continue
Is the issue clear enough to act on?
YES → Continue to Step 3
NO → Add `needs-info`, comment asking for clarification
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.
- 11d ago First seen · 213 lines · 60 tokens per session scan A 8835456931c8
gh-issue-triage is a skill published in the GitHub repository poindexter12/waypoint (7 stars, last pushed 7mo ago), licensed MIT. It adds 60 tokens to every session and 1,332 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.