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/amanning3390/hermeshub/github-workflownpx skills add amanning3390/hermeshub --skill github-workflowgit clone --depth 1 https://github.com/amanning3390/hermeshubWhat 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.00045 | $0.00622 |
| Opus 5 | $0.00023 | $0.00311 |
| Sonnet 5 | $0.00009 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
github-workflow 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 2d 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.
What it actually says
GitHub Workflow
Full GitHub lifecycle management through the gh CLI.
When to Use
- User mentions GitHub, repos, branches, commits, or pull requests
- User wants to manage issues, labels, or milestones
- User needs code review assistance
- User wants to set up CI/CD or manage releases
Procedure
Repository Operations
- Clone:
gh repo clone owner/repo - Create:
gh repo create name --public/--private - Fork:
gh repo fork owner/repo
Branch Workflow
- Create feature branch:
git checkout -b feature/name - Stage changes:
git add -A - Commit with conventional message:
git commit -m "type: description" - Push:
git push -u origin feature/name
Pull Request Workflow
- Create PR:
gh pr create --title "..." --body "..." --base main - List PRs:
gh pr list - Review PR:
gh pr review <number> --approve/--request-changes - Merge:
gh pr merge <number> --squash
Issue Management
- Create:
gh issue create --title "..." --body "..." --label bug - List:
gh issue list --state open - Close:
gh issue close <number> - Assign:
gh issue edit <number> --add-assignee @me
Release Workflow
- Tag:
git tag -a v1.0.0 -m "Release v1.0.0" - Push tags:
git push --tags - Create release:
gh release create v1.0.0 --generate-notes
Commit Message Convention
- feat: new feature
- fix: bug fix
- docs: documentation
- refactor: code restructuring
- test: adding tests
- chore: maintenance
Pitfalls
- Always check current branch before committing
- Pull before push to avoid conflicts
- Use --force-with-lease instead of --force
- Verify PR base branch is correct
Verification
- Confirm PR was created:
gh pr view <number> - Verify merge status:
gh pr status - Check CI status:
gh run list
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.
- 2d ago First seen · 74 lines · 45 tokens per session scan A 3ba9ac3b840f
github-workflow is a skill published in the GitHub repository amanning3390/hermeshub (34 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 622 once invoked, about $0.0002 per session on Opus 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-08-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
release
Create a new es-toolkit release (version bump, changelog, tag).
git-workflow
安全处理 Git 状态检查、提交信息、commit、分支、push、PR 和 rebase。用于用户要求检查改动、生成或创建提交、管理分支、推送、发起 PR 或整理历史时;严格区分每个动作的授权,并保护工作树中已有和无关的修改。.
zed-cherry-pick
Cherry-pick one or more merged PRs and/or commits into Zed's preview or stable release branch. Use this whenever the user mentions cherry-picking to preview/stable, a failed cherry-pick run, or wants to manually port fix(es) into a release branch.