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/jonathan-vella/apex-accelerator/github-operationsnpx skills add jonathan-vella/apex-accelerator --skill github-operationsgit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/github-operations)<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/github-operations"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/github-operations.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.00101 | $0.01256 |
| Opus 5 | $0.00051 | $0.00628 |
| Sonnet 5 | $0.00020 | $0.00251 |
| Haiku 4.5 | $0.00010 | $0.00126 |
Grade A, and why
github-operations 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Operations
Full contribution lifecycle — from branch creation to PR merge.
gh CLI preferred (always available in this dev container); MCP tools as
fallback for operations with no gh equivalent (rich PR review thread
management, bulk GraphQL queries).
Steps
1. Create branch (naming convention) →
2. Make changes →
3. Commit (conventional commits) →
4. Push (pre-push hooks validate branch + scope) →
5. Create PR (gh CLI) →
6. Review + Merge
Rules
- Identify the operation (issue, PR, search, Actions, release, etc.)
- Use
ghCLI by default — always available in this dev container; the more stable primitive - Fall back to MCP only when
ghcannot satisfy the operation (rich PR review threads, bulk GraphQL, Copilot review requests) - Validate branch name before any commit or PR —
git rev-parse --abbrev-ref HEAD; if invalid, stop and rename viagit branch -m - Conventional Commits are mandatory — enforced by commitlint
- Devcontainer: do not run
gh auth login;GH_TOKENis set via VS Code User Settings (terminal.integrated.env.linux) - Never skip hooks (
--no-verify) unless the user explicitly asks
Branch Naming Quick Reference
| Type | Prefixes | File Scope |
|---|---|---|
| Domain-scoped | docs/, agents/, skills/, infra/, scripts/, instructions/ |
Restricted to domain paths |
| Cross-cutting | feat/, fix/, chore/, ci/, refactor/, perf/, test/, build/, revert/ |
Any files |
For scope tables, validation commands, and enforcement layers, read
references/branch-strategy.md.
Conventional Commits Quick Reference
Format: <type>[optional scope]: <description>.
Types: feat, fix, docs, refactor, perf, test, build, ci,
chore, revert.
What ships with it
5 files 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.
- yesterday First seen · 115 lines · 101 tokens per session scan A 8a515b4c4340
github-operations is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 1,256 once invoked, about $0.0005 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
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
release-process
Operate Squad's automated insider, preview, and stable release channels safely.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
shep-kit:commit-pr
Use when ready to commit, push, and create a PR with CI verification. Triggers include "commit and pr", "push pr", "create pr", "ship it", or when implementation is complete and needs CI validation. Watches CI and auto-fixes failures. Part of the Shep autonomous SDLC platform — https://shep.bot.