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 runxhq/runx --skill githubgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/github)<a href="https://agentmods.dev/skills/runxhq/runx/github"><img src="https://agentmods.dev/badge/skills/runxhq/runx/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/runxhq/runx/github"><img src="https://agentmods.dev/badge/skills/runxhq/runx/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.00028 | $0.01604 |
| Opus 5.5 | $0.00011 | $0.00642 |
| Sonnet 5.5 | $0.00006 | $0.00321 |
| Haiku 4.5 | $0.00003 | $0.00160 |
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 4d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub
Define one bounded synchronization between local Runx state and a GitHub repository. The skill makes direction, resource set, filters, content identity, scope, cursor, and authority posture explicit before the selected GitHub instance is allowed to read or mutate GitHub.
The default github runner performs the requested pull or push. plan
is the explicit no-effect runner; pull and push remain explicit execution
lanes for compatible callers. Pulls are bounded reads. A push carries one to
twenty typed mutations per call that one GitHub operation applies, and returns each
item's outcome. It closes only on an independent GitHub readback of every
applied item. An item whose outcome is unknown holds the push for
reconciliation and is never silently retried. activity reads what changed
in a repository since a time, compact enough to summarise. No GitHub token
enters this package.
When to use it
Use github when an operator needs a reproducible pull or push contract for
issues, pull requests, or threads, especially when cursor state must survive
across runs. Use plan only when the requested outcome is a plan. Use pull
for an explicitly selected read lane. Use activity to learn what changed in
a repository since a time, such as since the last check of a daily summary:
it reads issues and pull requests together and returns the fields a reader
needs rather than GitHub's whole records. Use push for already-decided issue,
pull-request, or comment changes of one kind. A call accepts up to twenty changes, matching the connector's batch contract; split larger work into separate calls and retain each result. Batches are bounded and
best-effort, not atomic: a refused item does not stop the rest, the result
identifies each item, and the operator reconciles before retrying. Use github-issue-triage to decide what an issue means
and github-issue-to-pr to govern an implementation lane.
Do not use a plan as evidence that remote state was read or changed. Only the
native runx.provider.operation.v1 result from pull or push is provider
evidence. Do not silently turn a denied push into a pull.
What ships with it
31 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.
- fixtures/activity-reads-what-changed-since.yaml 2.7 KB
- fixtures/bin/gh 205 B
- fixtures/boolean-pull-base-blocked.yaml 401 B
- fixtures/comment-plan-scope.yaml 550 B
- fixtures/comment-posts-and-verifies.yaml 2.8 KB
- fixtures/comment-requires-github-binding.yaml 642 B
- fixtures/composes-in-graph.yaml 164 B
- fixtures/missing-direction-needs-agent.yaml 301 B
- fixtures/mixed-push-blocked.yaml 686 B
- fixtures/nul-assignee-blocked.yaml 412 B
- fixtures/nul-label-blocked.yaml 402 B
- fixtures/nul-thread-body-blocked.yaml 423 B
- fixtures/null-mutation-field-blocked.yaml 411 B
- fixtures/null-pull-base-blocked.yaml 395 B
- fixtures/numeric-pull-base-blocked.yaml 400 B
- fixtures/oversized-mutation-blocked.yaml 667 B
- fixtures/plan-and-append-cursor-sqlite.yaml 1.7 KB
- fixtures/pull-continues-from-cursor-page.yaml 1.3 KB
- fixtures/pull-open-issues-read-only.yaml 1.8 KB
- fixtures/push-labels-applies-and-reads-back.yaml 2.1 KB
- fixtures/push-labels-scoped-write.yaml 705 B
- fixtures/push-opens-issue-and-reads-back.yaml 2.4 KB
- fixtures/support/composed.graph 439 B
- fixtures/twenty-issue-updates-plan.yaml 1.8 KB
- fixtures/twenty-one-issue-updates-refused.yaml 1.6 KB
- fixtures/write-without-grant-refused.yaml 563 B
- github.mjs 7.6 KB runs code
- github.test.mjs 3.2 KB runs code
- packets/sync_plan.v1.schema.json 2.5 KB
- references/catalog.md 149 B
- run.yaml 26 KB
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.
- 4d ago Changed 344771bc1126
- 5d ago Changed ea3df40a280e
- 9d ago Changed · +17 lines ea5c3e7805f5
- 12d ago First seen · 102 lines · 28 tokens per session scan A 90bb41315945
github is a skill published in the GitHub repository runxhq/runx (105 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 1,604 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-10-18.
Other skills, from other repositories
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.