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 commands/notque/vexjoy-agent/github-notificationsWrote 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/commands/notque/vexjoy-agent/github-notifications)<a href="https://agentmods.dev/commands/notque/vexjoy-agent/github-notifications"><img src="https://agentmods.dev/badge/commands/notque/vexjoy-agent/github-notifications/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/commands/notque/vexjoy-agent/github-notifications"><img src="https://agentmods.dev/badge/commands/notque/vexjoy-agent/github-notifications.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.00014 | $0.00202 |
| Opus 5.5 | $0.00006 | $0.00081 |
| Sonnet 5.5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
github-notifications 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.
What it actually says
Triage GitHub notifications: fetch, classify, report actions needed.
Usage: /github-notifications [--mark-read] [--save]
Default: report-only (shows what needs attention, doesn't modify anything) --mark-read: also mark informational notifications as read --save: save report to ~/.claude/reports/notifications/
Invokes: scripts/github-notification-triage.py
Instructions for Claude
Arguments: "$ARGUMENTS"
Parse arguments from $ARGUMENTS, then run:
python3 scripts/github-notification-triage.py $ARGUMENTS
Present the output to the user. If the report includes informational notifications and --mark-read was not passed, ask the user if they want to clear them.
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 · 28 lines · 14 tokens per session scan A 14b7a2a584e7
github-notifications is a command published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 202 once invoked, about $0.0001 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 commands, from other repositories
retro
Run a sprint retrospective with data-driven insights from git history.
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.