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 agentmods add skills/christosk92/waveemusic/github-triagenpx skills add christosk92/WaveeMusic --skill github-triagegit clone --depth 1 https://github.com/christosk92/WaveeMusicWrote 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/christosk92/waveemusic/github-triage)<a href="https://agentmods.dev/skills/christosk92/waveemusic/github-triage"><img src="https://agentmods.dev/badge/skills/christosk92/waveemusic/github-triage.svg" alt="Measured on agentmods" 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 | $0.00079 | $0.03669 |
| Opus 5 | $0.00039 | $0.01835 |
| Sonnet 5 | $0.00016 | $0.00734 |
| Haiku 4.5 | $0.00008 | $0.00367 |
Grade A, and why
github-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 yesterday.
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub triage for Wavee (labels · milestones · project · templates)
Rule zero — always ask for manual approval. Before any gh (or gh api) call that changes something on
GitHub — labels, milestones, issue/PR edits, comments, project items, repo settings, pushes, PR creation — stop
and ask with AskUserQuestion, listing the exact commands. Batch them into one question, run only what was
approved, then report what changed. Read-only calls (gh issue list, gh label list, gh project view,
gh repo view, gh api GET …) need no approval. Never run gh auth refresh / gh auth login yourself: it is a
device-code flow — tell the user the command (! gh auth refresh -s project,read:project) and wait.
There is no CI: everything below is applied locally with gh from the dev box, exactly like releases.
What exists (set up 2026-09-01)
| Thing | Where | Notes |
|---|---|---|
| Label set (53) | ops/github/labels.json → applied by ops/github/sync-labels.ps1 |
source of truth; idempotent; never deletes; renames the 7 stock labels in place |
| Label test | ops/release/tests/GitHub.Labels.Tests.ps1 |
pure Pester 3.4 syntax (Should Be); runs with Invoke-Pester -Path ops/release/tests |
| Milestones | GitHub | 0.2.x Breaker (#1), 0.3 Crest (#2), 0.4 Drift (#3), Future (#4) — one per minor codename; patches inherit the minor's milestone |
| Project board | https://github.com/users/christosk92/projects/3 (number 3, public, linked to the repo) | id PVT_kwHOAM0O7s4BiKKu; Status field PVTSSF_lAHOAM0O7s4BiKKuzhhDNNI (Triage · Backlog · Planned · In progress · In review · Done); Priority field PVTSSF_lAHOAM0O7s4BiKKuzhhDNN8 (P0–P3) |
| Issue forms | .github/ISSUE_TEMPLATE/{bug_report,crash_report,feature_request}.yml + config.yml |
blank issues off; contact links → Discussions Q&A / Ideas, fluent-gpu issues, Store listing |
| PR template | .github/PULL_REQUEST_TEMPLATE.md |
the Debug+Release / tests / changelog / no-source-text-tests gates |
| Contributor docs | CONTRIBUTING.md, SECURITY.md |
label scheme, branch/commit conventions, private vulnerability reporting |
| Repo settings | GitHub | Discussions on (default categories), wiki off, delete-branch-on-merge on, private vulnerability reporting on, homepage = Store listing, topics set |
| Token scopes | gh auth status |
repo, read:org, gist, project — project is required for anything under gh project |
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.
- yesterday First seen · 165 lines · 79 tokens per session scan A 82ce69e093c8
github-triage is a skill published in the GitHub repository christosk92/WaveeMusic (50 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 3,669 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
dpg-migration
Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.
mitigate-breaking-changes
Patterns and techniques for mitigating breaking changes in Azure management-plane SDKs. Covers SDK-side customizations (partial classes, CodeGenType, CodeGenSuppress) and TypeSpec decorator customizations (clientName, access, markAsPageable, alternateType, hierarchyBuilding).
generate-code-cs
Generate the code from typespec for C#. Parameter: C# SDK repository root location .
author-test
Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.
nunit-code-style
Use when writing or modifying C# method bodies, type declarations, or non-trivial logic in NUnit source. Covers NUnit's taste-and-judgment conventions — exception construction, simplification, naming intent, StringComparison, non-null check form, and var usage — that aren't already caught at build time.
nunit-api-design
Use when adding or modifying public API surface in NUnit — new or changed constraints, attributes, assertions, helpers, or any type/member visibility change. Covers the conventions NUnit maintainers enforce for types that ship to consumers of the framework.