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 geezerrrr/motive --skill githubgit clone --depth 1 https://github.com/geezerrrr/motiveWrote 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/geezerrrr/motive/github)<a href="https://agentmods.dev/skills/geezerrrr/motive/github"><img src="https://agentmods.dev/badge/skills/geezerrrr/motive/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/geezerrrr/motive/github"><img src="https://agentmods.dev/badge/skills/geezerrrr/motive/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.00044 | $0.00441 |
| Opus 5.5 | $0.00018 | $0.00176 |
| Sonnet 5.5 | $0.00009 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
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 1mo 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.
This is a copy
98% identical to github — 35 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
GitHub Skill
Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.
Pull Requests
Check CI status on a PR:
gh pr checks 55 --repo owner/repo
List recent workflow runs:
gh run list --repo owner/repo --limit 10
View a run and see which steps failed:
gh run view <run-id> --repo owner/repo
View logs for failed steps only:
gh run view <run-id> --repo owner/repo --log-failed
API for Advanced Queries
The gh api command is useful for accessing data not available through other subcommands.
Get PR with specific fields:
gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'
JSON Output
Most commands support --json for structured output. You can use --jq to filter:
gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'
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.
- 1mo ago First seen · 78 lines · 44 tokens per session scan A b1dfa8cd04bc
github is a skill published in the GitHub repository geezerrrr/motive (120 stars, last pushed 6d ago), licensed MIT. It adds 44 tokens to every session and 441 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to github, differing in 35 lines, and is treated as a copy.
Other skills, from other repositories
worktree-enhanced
Sets up a git worktree for isolated feature work: creates the branch, configures the worktree, detects a running dev server, and handles project setup. Trigger on: "create a worktree", "start work on issue #X", "start a feature branch", "work on this in isolation".
post-merge
Runs after a PR merges: syncs the base branch, deletes the merged branch and worktree, closes out linked issues without asking (even on a develop base), then recommends the next issue. Trigger on: "merged PR #42", "PR is merged", "just merged the auth fix", "I merged #123".
github-screenshot
Generates GitHub-ready image markdown for screenshots using raw.githubusercontent.com URLs via generate-github-image-markdown.sh. Use whenever a PR, issue, or doc needs an image. Trigger on: "add a screenshot to this PR", "embed image in issue", "attach screenshot", "add screenshot to docs".
pr-review-fix-pipeline
Reviews a PR and applies fixes for the non-controversial findings: review, fix, test, and commit in one pass. Writes code, so use it only on feature branches where automatic edits are fine. Trigger on: "review and fix PR", "auto-fix the PR", "review PR #X and fix issues", "run the review pipeline".
ship-issue
Drives one GitHub issue from cold start to merged PR: sync, analyze, minimal fix with a test, PR, CI green, merge, post-merge cleanup, wrap-up. Trigger on: "ship issue #X", "ship #123", "take #N to merge", "do issue #X end to end".
backlog-routing
Works a GitHub milestone with several agents at once: intake findings as issues, shape and batch the milestone, route batches to the cheapest capable model, dispatch, review, release. Merge authority comes from the repo adapter. Trigger on: "route the backlog", "plan the milestone", "dispatch the batches", "file…