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 stabruriss/kota-app --skill githubgit clone --depth 1 https://github.com/stabruriss/kota-appWrote 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/stabruriss/kota-app/github)<a href="https://agentmods.dev/skills/stabruriss/kota-app/github"><img src="https://agentmods.dev/badge/skills/stabruriss/kota-app/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/stabruriss/kota-app/github"><img src="https://agentmods.dev/badge/skills/stabruriss/kota-app/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.00053 | $0.00950 |
| Opus 5.5 | $0.00021 | $0.00380 |
| Sonnet 5.5 | $0.00011 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
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
100% identical to github — 85 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub
Overview
Use this skill as the umbrella entrypoint for general GitHub work in this plugin. It should decide whether the task stays in repo and PR triage or should be handed off to a more specific review, CI, or publish workflow.
This plugin is intentionally hybrid:
- Prefer the GitHub app from this plugin for repository, issue, pull request, comment, label, reaction, and PR creation workflows.
- Use local
gitandghonly when the connector does not cover the job well, especially for current-branch PR discovery, branch creation, commit and push,gh auth status, and GitHub Actions log inspection. - Keep connector state and local checkout context aligned. If the request is about the current branch, resolve the local repo and branch before acting.
Once the intent is clear, route to the specialist skill immediately and do not keep broad GitHub triage in scope longer than needed.
Connector-First Responsibilities
Handle these directly in this skill when the request does not need a narrower specialist workflow:
- repository orientation once the repo, PR, issue, or local checkout is identified
- recent PR or issue triage
- PR metadata summaries
- PR patch inspection
- PR comments, labels, and reactions
- issue lookup and summarization
- PR creation after a branch is already pushed
Prefer the GitHub app from this plugin for those flows because it provides structured PR, issue, and review-adjacent data without depending on a local checkout. If the repository is not already identifiable from the user request or local git context, ask for the repo instead of pretending there is a repo-search flow that may not exist.
Routing Rules
- Resolve the operating context first:
- If the user provides a repository, PR number, issue number, or URL, use that.
- If the request is about "this branch" or "the current PR", resolve local git context and use
ghonly as needed to discover the branch PR. - If the repository is still ambiguous after local inspection, ask for the repo identifier.
- Classify the request before taking action:
repo or PR triage: summarize PRs, issues, patches, comments, labels, reactions, or repository statereview follow-up: unresolved review threads, requested changes, or inline review feedbackCI debugging: failing checks, Actions logs, or CI root-cause analysispublish changes: create or switch branches, stage changes, commit, push, and open a draft PR
- Route to the specialist skill as soon as the category is clear:
- Review comments and requested changes:
../gh-address-comments/SKILL.md - Failing GitHub Actions checks:
../gh-fix-ci/SKILL.md - Commit, push, and open PR:
../yeet/SKILL.md
- Review comments and requested changes:
- Keep the hybrid model consistent after routing:
- connector first for PR and issue data
- local
gitandghonly for the specific gaps the connector does not cover
What ships with it
3 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.
- 1mo ago First seen · 75 lines · 53 tokens per session scan A 81dbdd90934f
github is a skill published in the GitHub repository stabruriss/kota-app (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 53 tokens to every session and 950 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to github, differing in 85 lines, and is treated as a copy.
Other skills, from other repositories
standup-update
Generate a concise standup update from the user's recent work GitHub activity, including the previous work period and today. Use when the user asks what they worked on, requests a standup update, or invokes /standup.
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
github-operations
A tool for managing GitHub pull requests and issues. Pull requests are proposed code changes for review, while issues are GitHub's way to track bugs, tasks, and questions.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.