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-templatesgit 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-templates)<a href="https://agentmods.dev/skills/poindexter12/waypoint/gh-issue-templates"><img src="https://agentmods.dev/badge/skills/poindexter12/waypoint/gh-issue-templates/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-templates"><img src="https://agentmods.dev/badge/skills/poindexter12/waypoint/gh-issue-templates.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.00049 | $0.00842 |
| Opus 5.5 | $0.00020 | $0.00337 |
| Sonnet 5.5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
gh-issue-templates 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 1mo 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Templates
Standardized formats for creating GitHub issues with consistent structure.
Quick Reference
| Type | Title Prefix | Key Sections |
|---|---|---|
| Bug | bug: |
Describe, Expected, Steps, Environment |
| Feature | feat: |
Problem, Solution, Alternatives, Acceptance |
| Task | task: or chore: |
Description, Checklist, Context |
Bug Report Format
Title: bug: <short description>
Body:
## Describe the bug
<!-- What happened? -->
## Expected behavior
<!-- What should have happened? -->
## Steps to reproduce
1.
2.
3.
## Environment
- OS:
- Version:
- Relevant config:
## Logs/Screenshots
<!-- If applicable -->
Bug Examples
Good:
bug: login fails with expired OAuth tokenbug: dashboard crashes when filter is empty
Bad:
bug: it's brokenbug: doesn't work
Feature Request Format
Title: feat: <short description>
Body:
## Problem
<!-- What problem does this solve? -->
## Proposed solution
<!-- How should it work? -->
## Alternatives considered
<!-- Other approaches you thought of -->
## Acceptance criteria
<!-- How do we know it's done? -->
- [ ] Criterion 1
- [ ] Criterion 2
Feature Examples
Good:
feat: add CSV export for reportsfeat: support dark mode in settings
Bad:
feat: make it betterfeat: new feature
Task Format
Title: task: <short description> or chore: <short description>
Use task: for project work, chore: for maintenance/deps/infra.
Body:
## Description
<!-- What needs to be done? -->
## Checklist
- [ ] Step 1
- [ ] Step 2
- [ ] Step 3
## Context
<!-- Why is this needed? -->
Task Examples
Good:
task: set up CI pipelinechore: upgrade React to v19chore: update dependencies
Bad:
task: do the thingchore: stuff
Template Selection Guide
Is something broken?
YES → Bug Report
NO → Continue
Is this new functionality?
YES → Feature Request
NO → Continue
Is this maintenance/infrastructure?
YES → Task (chore:)
NO → Task (task:)
What ships with it
3 files 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.
- 1mo ago First seen · 157 lines · 49 tokens per session scan A c0abd0c871f8
gh-issue-templates is a skill published in the GitHub repository poindexter12/waypoint (7 stars, last pushed 9mo ago), licensed MIT. It adds 49 tokens to every session and 842 once invoked, about $0.0002 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-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.