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 agentmods add skills/soulcynics404/agentforge/github-automationnpx skills add Soulcynics404/AgentForge --skill github-automationgit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/soulcynics404/agentforge/github-automation)<a href="https://agentmods.dev/skills/soulcynics404/agentforge/github-automation"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/github-automation.svg" alt="Measured on agentmods" 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 | $0.00061 | $0.00352 |
| Opus 5 | $0.00030 | $0.00176 |
| Sonnet 5 | $0.00012 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
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 yesterday.
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-automation — 0 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 Automation Skill
Purpose
GitHub workflow automation, PR management, and repository coordination.
When to Trigger
- Creating pull requests
- Managing issues
- Setting up CI/CD workflows
- Code review automation
- Release management
Commands
Create Pull Request
gh pr create --title "feat: description" --body "## Summary\n..."
Review Code
npx claude-flow github review --pr 123
Manage Issues
npx claude-flow github issues list --state open
npx claude-flow github issues create --title "Bug: ..."
Setup Workflow
npx claude-flow workflow create --template ci
Release Management
npx claude-flow deployment release --version 1.0.0
Agent Types
| Agent | Role |
|---|---|
pr-manager |
Pull request lifecycle |
code-review-swarm |
Automated code review |
issue-tracker |
Issue management |
release-manager |
Release automation |
workflow-automation |
GitHub Actions |
Best Practices
- Use conventional commits
- Require reviews before merge
- Run CI on all PRs
- Automate release notes
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.
- yesterday First seen · 64 lines · 61 tokens per session scan A 5e9ebc25b95b
github-automation is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 11d ago), licensed MIT. It adds 61 tokens to every session and 352 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to github-automation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ship
Commit and push the current work properly — lint, run the release gate, write a detailed commit message, push to GitHub. Use whenever work reaches a milestone or the user says ship it, commit, or push.
git-ship
Use this skill whenever the user wants to commit, push, or ship changes in a git repository. Triggers include: "commit changes", "push my changes", "ship it", "commit and push", "create a branch and commit", "make a PR", "open a pull request", "create draft PR", or any variation of committing/pushing work. Always use…
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
writing-commits-and-prs
Apply the repository writing rules to commits, pull requests, branches, changelogs, and release notes.
git
Run git version control commands for repository management. Use when the user asks to check status, view history or diffs, stage and commit changes, manage branches, merge or rebase, work with remotes, stash changes, tag releases, cherry-pick commits, bisect regressions, resolve conflicts, manage worktrees or…
release-notes
Maintain Mozaiks release notes proactively. Use when changing released behavior, preparing a PyPI/GitHub release, bumping versions, modifying generated app scaffolds, changing public install/setup docs, or reviewing whether a change needs a changelog entry.