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/aaronnat23/disp8ch/github-pr-workflownpx skills add aaronnat23/disp8ch --skill github-pr-workflowgit clone --depth 1 https://github.com/aaronnat23/disp8chWhat 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.00000 | $0.00180 |
| Opus 5 | $0.00000 | $0.00090 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
github-pr-workflow 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 2d 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
GitHub PR Workflow
Handle pull-request work as a clean sequence: inspect, review, patch, verify, and summarize.
Use when
- A user asks for PR review, follow-up commits, or merge-readiness checks.
- GitHub issues, PRs, and repo state all matter to the answer.
Workflow
- Identify the repo, branch, PR, or issue context first.
- Read the diff and classify risk before proposing changes.
- Prefer concrete findings: bug risk, missing tests, rollback risk, or docs drift.
- If code changes are needed, patch the smallest safe scope and verify locally.
- End with a concise PR-style summary: findings, fixes, tests, and open risks.
Deliverable
- Clear review findings or implementation outcome.
- Relevant repo/PR references.
- Verification summary.
- Remaining blockers before merge.
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.
- 2d ago First seen · 21 lines · 0 tokens per session scan A 78299f49ae86
github-pr-workflow is a skill published in the GitHub repository aaronnat23/disp8ch (98 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 180 tokens. 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 skills, from other repositories
add-dashboard-orpc-procedure
Verify permission guards when creating, modifying, or reviewing any oRPC procedure file in packages/xinity-ai-dashboard/src/lib/server/orpc/procedures/.
run-tests
End-to-end verification that every test suite in the workspace runs green locally. Use when validating dependency changes, refactors, or anything else that could plausibly affect runtime behavior across packages.
add-env-variable
Add a new environment variable to any service package following the env-schema / parseEnv pattern with Zod schema, describe(), and meta(secret()) annotations.
code-quality-control
Apply repo quality standards (comments, naming, simplicity, structure) when reviewing or writing code. Use as a checklist before completing work on any file.
integrate-model
Integrate a new inference model into Xinity from a loose request like "install/integrate/add model X". Researches the model, assembles validated model data (the xinity-infoserver model entry), and verifies it actually runs via the daemon's run-model script, iterating on failures. Use whenever someone wants to make a…
modularity-review
Review codebase or design for modularity problems and produce actionable improvement recommendations. Also guides design of new modular boundaries from functional requirements. Inspired by Vlad Khononov's balanced-coupling model and golden-age-of-modularity principles. NOTE: Full upstream plugin at…