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 tmolavi/mcp-agent-skills-hub --skill github-automationgit clone --depth 1 https://github.com/tmolavi/mcp-agent-skills-hubWrote 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/tmolavi/mcp-agent-skills-hub/github-automation)<a href="https://agentmods.dev/skills/tmolavi/mcp-agent-skills-hub/github-automation"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/github-automation/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/tmolavi/mcp-agent-skills-hub/github-automation"><img src="https://agentmods.dev/badge/skills/tmolavi/mcp-agent-skills-hub/github-automation.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.00048 | $0.03011 |
| Opus 5 | $0.00024 | $0.01505 |
| Sonnet 5 | $0.00010 | $0.00602 |
| Haiku 4.5 | $0.00005 | $0.00301 |
Grade A, and why
github-automation 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 6d 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
92% identical to github-automation — 8 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Automation via Rube MCP
Automate GitHub repository management, issue tracking, pull request workflows, branch operations, and CI/CD through Composio's GitHub toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active GitHub connection via
RUBE_MANAGE_CONNECTIONSwith toolkitgithub - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitgithub - If connection is not ACTIVE, follow the returned auth link to complete GitHub OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create and Manage Issues
When to use: User wants to create, list, or manage GitHub issues
Tool sequence:
GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER- Find target repo if unknown [Prerequisite]GITHUB_LIST_REPOSITORY_ISSUES- List existing issues (includes PRs) [Required]GITHUB_CREATE_AN_ISSUE- Create a new issue [Required]GITHUB_CREATE_AN_ISSUE_COMMENT- Add comments to an issue [Optional]GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS- Search across repos by keyword [Optional]
Key parameters:
owner: Repository owner (username or org), case-insensitiverepo: Repository name without .git extensiontitle: Issue title (required for creation)body: Issue description (supports Markdown)labels: Array of label namesassignees: Array of GitHub usernamesstate: 'open', 'closed', or 'all' for filtering
Pitfalls:
GITHUB_LIST_REPOSITORY_ISSUESreturns both issues AND pull requests; checkpull_requestfield to distinguish- Only users with push access can set assignees, labels, and milestones; they are silently dropped otherwise
- Pagination:
per_pagemax 100; iterate pages until empty
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.
- 6d ago First seen · 236 lines · 48 tokens per session scan A 3a9365f940e6
github-automation is a skill published in the GitHub repository tmolavi/mcp-agent-skills-hub (8 stars, last pushed 14d ago), licensed MIT. It adds 48 tokens to every session and 3,011 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to github-automation, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
release-notes-generator
A writing tool that turns a plain-text sprint summary or product update into release notes for a changelog, email, in-app message, and social post.
github
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way. Automatically runs the code-review skill before any commit. Enforces Conventional Commits standard. Handles the full lifecycle: branch → review → commit → push → PR.
change-tracker
Automated Markdown changelog and version history maintenance during development. / TR: Kod yazıldıkça yapılan değişiklikleri (changelog) ve versiyon geçmişini standart Markdown dosyasında tutma kuralı.
Git Conventional Commits
Git commit message and branch naming standards following Conventional Commits format. / TR: Git commit mesajları ve branch isimlendirme standartlarını belirler. Conventional Commits kurallarını uygular.
Git PR Reviewer
Pull Request (PR) creation and code review standards with constructive feedback and merge strategies. / TR: Pull Request (PR) oluşturma ve kod inceleme (code review) süreçleri için standartlar ve yapıcı geri bildirim.
commit
Detect the repo's commit convention (Conventional Commits, Gitmoji, or a custom template) and create commits. Use when asked to commit, write a commit message, stage and commit changes, or commit and push work.