Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/notque/vexjoy-agentnpx agentmods add skills/notque/vexjoy-agent/github-notification-triageWrote 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/notque/vexjoy-agent/github-notification-triage)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/github-notification-triage"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/github-notification-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.1 | $0.00018 | $0.00693 |
| Opus 5 | $0.00009 | $0.00347 |
| Sonnet 5 | $0.00004 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
github-notification-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 3d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Notification Triage Skill
Fetch, classify, and report on GitHub notifications. The script does the heavy lifting — this skill orchestrates invocation and presents results.
Commands
# Report-only (default): show what needs attention, no modifications
python3 scripts/github-notification-triage.py
# Mark informational notifications as read after reporting
python3 scripts/github-notification-triage.py --mark-read
# Save report to ~/.claude/reports/notifications/
python3 scripts/github-notification-triage.py --save
# Cron/scheduled mode: auto-clear noise and save report
python3 scripts/github-notification-triage.py --mark-read --save
Instructions
Step 1: Run the triage script
Run report-only by default:
python3 scripts/github-notification-triage.py
Step 2: Present the report
Display the script output directly to the user. The report classifies notifications into:
- Action required — PRs awaiting review, mentions, assigned issues
- Informational — CI results, bot comments, automated updates (safe to clear)
Step 3: Handle follow-up
If the user responds with any of the following, re-run with --mark-read:
- "clean them up"
- "mark read"
- "clear the noise"
- "yes" (in response to a prompt about clearing informational items)
python3 scripts/github-notification-triage.py --mark-read
Confirm how many notifications were marked read after the run completes.
Cron/scheduled mode
When invoked on a schedule (no interactive user), use both flags to auto-clear and persist the report:
python3 scripts/github-notification-triage.py --mark-read --save
Reference Loading Table
| Signal | Load These Files | Why |
|---|---|---|
| triaging an issue or pull-request queue | item-card-contract.md |
Defines the required per-item report card. |
Issue/PR Queue Triage
When the task is triaging a queue of issues or PRs (not just notifications), report one card per item using the contract in references/item-card-contract.md:
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.
- 3d ago First seen · 103 lines · 18 tokens per session scan A 5bd5a65215c7
github-notification-triage is a skill published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 693 once invoked, about $0.0001 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
utility-pm-release-conductor
Walk the guided 6-gate release runbook (G0 readiness, G1 adversarial review, G2 version bump and CHANGELOG, G2.5 commit and re-verify, G3 tag and push, G4 post-tag hygiene) via the pm-release-conductor sub-agent. Refuses gate bypasses and tags only the re-verified SHA. Use when cutting a pm-skills release.
epic-dev
Execute the project epic development workflow for Codex. Use when the user asks for "epic dev", "epic-dev", "/epic-dev", "run the epic workflow", "create an epic", "resume the epic", "--resume", "--next-phase", "--finalize", phased feature delivery, sprint phases, GitHub sub-issues, or git worktrees for multi-phase…
workflow-reference
This skill should be used when executing the epic-dev workflow, creating epic branches, managing sprint phases, working with git worktrees for phased feature development, or when the user mentions "epic dev", "epic-dev", "/epic-dev", "epic workflow", "sprint phases", "phased development", or "git worktree workflow".
github-digest
You are a GitHub assistant generating a daily PR + issues digest for the user.
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
ds-ship
Ship orchestrator — classify the project, pick a mode (improve/release/launch/maintain), delegate only the skills the project's signals justify, consolidate findings, produce an audit report. Use for an end-to-end audit or ship pipeline across multiple skills.