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/githubWrote 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)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/github"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/github/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/notque/vexjoy-agent/github"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/github.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.00013 | $0.00941 |
| Opus 5.5 | $0.00005 | $0.00376 |
| Sonnet 5.5 | $0.00003 | $0.00188 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
github 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 25d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Skill
GitHub notification triage and issue/PR queue classification.
Mode Selection
| Request | Mode |
|---|---|
| Notifications, inbox, cleanup | Notification Triage |
| Issue or PR queue, review items | Queue Triage |
Notification Triage
Fetch, classify, and report GitHub notifications via the triage script.
Commands
# Report-only (default)
python3 scripts/github-notification-triage.py
# Mark informational notifications as read
python3 scripts/github-notification-triage.py --mark-read
# Save report to ~/.claude/reports/notifications/
python3 scripts/github-notification-triage.py --save
# Cron/scheduled: auto-clear noise and save
python3 scripts/github-notification-triage.py --mark-read --save
Steps
- Run report-only:
python3 scripts/github-notification-triage.py. - Display the output. The report classifies notifications as:
- Action required -- PRs awaiting review, mentions, assigned issues.
- Informational -- CI results, bot comments, automated updates.
- If the user says "clean them up", "mark read", "clear the noise", or "yes"
to clearing informational items, re-run with
--mark-read. Confirm how many were marked read.
Scheduled (no interactive user): run with --mark-read --save.
Exit codes: 0 = success, 1 = error (auth, API, script not found).
Queue Triage
When triaging a queue of issues or PRs (not just notifications), produce one card per item.
Card Format
Open each card with the item's full GitHub URL on its own line, then these fields in order:
| Field | Content |
|---|---|
| What | One sentence: what the issue/PR asks or changes. |
| Why | Motivation or problem it addresses. |
| Author trust | Maintainer, known contributor, first-timer, or bot. Cite prior merged PRs. |
| Fit | Match to project scope and conventions. |
| Risk | Blast radius: files touched, API/behavior changes, security or data paths. |
| Proof state | CI status, tests added, repro steps, screenshots. "Unverified" when none. |
| Blocker | Single thing stopping progress, or "None". |
| Next action | One concrete step with named actor. Label Autonomous or Needs-owner. |
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.
- 26d ago Changed · -92 lines · +10 tokens per session 92b5fba005f7
- 27d ago First seen · 130 lines · 13 tokens per session scan A ca6e5d49c388
github is a skill published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 941 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-09-20.
Other skills, from other repositories
utility-pm-skill-iterate
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
om-auto-fix-issue
Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain (om-verify-in-repo, om-root-cause, om-fix, om-open-pr, om-auto-review-pr, om-auto-qa-pr for UI fixes) or the feature…
foundation-stakeholder-update
Produces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference. Translates meeting outcomes into what-it-means language for readers, with channel variants (slack, teams, email, notion, exec-memo) and audience variants (engineering, design, leadership…
utility-pm-critic
Run adversarial review on a PM artifact via the pm-critic sub-agent. Returns findings graded P0/P1/P2/P3 with a concrete fix suggestion per finding and a machine-readable status block. Use after producing a PRD, meeting recap, OKR set, persona, or any PM artifact you want stress-tested before it ships.
utility-pm-skill-auditor
Run a repo-wide cross-cutting governance audit via the pm-skill-auditor sub-agent. Aggregates the enforcing validator suite, re-derives aggregate counters, and surfaces cross-cutting issues no single validator catches, graded P0/P1/P2/P3 with a machine-readable status. Use for pre-release readiness checks or a…