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 skills add jonathan-vella/apex-accelerator --skill apex-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/apex-github-operations)<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-github-operations"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-github-operations/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/jonathan-vella/apex-accelerator/apex-github-operations"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-github-operations.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.00104 | $0.01369 |
| Opus 5.5 | $0.00042 | $0.00548 |
| Sonnet 5 | $0.00021 | $0.00274 |
| Haiku 4.5 | $0.00010 | $0.00137 |
Grade A, and why
apex-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 today.
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 — 124 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 authunless explicitly asked to troubleshoot authentication. Use configured CLI credentials; never request tokens through chat or switch identity implicitly. - 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
What ships with it
7 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.
- today First seen · 124 lines · 104 tokens per session scan A 9177bedc85a7
apex-github-operations is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 104 tokens to every session and 1,369 once invoked, about $0.0004 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-23.
Other skills, from other repositories
versioning-policy
SemVer rules for Squad's stable, preview, insider, and local package versions.
land
Takes a committed branch from local to merged — pushes it, confirms which GitHub account each tool actually acts as in this repo, opens the PR through the one that matches (github-mcp where loaded, gh where its login is confirmed), then fast-forwards main, reports CI, and deletes the merged branch locally and on…
gh-cli
GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organisations, extensions, and all GitHub operations from the command line.
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.
changelog-scan
Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.