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/mamahoos/dot-files/github-workflownpx skills add mamahoos/dot-files --skill github-workflowgit clone --depth 1 https://github.com/mamahoos/dot-filesWrote 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/mamahoos/dot-files/github-workflow)<a href="https://agentmods.dev/skills/mamahoos/dot-files/github-workflow"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/github-workflow.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.00030 | $0.02255 |
| Opus 5 | $0.00015 | $0.01128 |
| Sonnet 5 | $0.00006 | $0.00451 |
| Haiku 4.5 | $0.00003 | $0.00226 |
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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflow
Git history is git-workflow-and-versioning. This skill is GitHub: issues, labels, assignees, reviews, merge.
Docs: linking PRs, sub-issues, labels.
Verification is mandatory. gh pr merge is not allowed while any linked body still contains an unchecked - [ ] or * [ ].
0. Discover (every repo, every time)
OWNER_REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
gh repo view --json nameWithOwner,defaultBranchRef,viewerPermission
gh label list
gh api "repos/${OWNER_REPO}/collaborators" --jq '.[] | {login, role_name}'
gh api "repos/${OWNER_REPO}/contents/.github/CODEOWNERS" >/dev/null 2>&1 || true
ls .github/PULL_REQUEST_TEMPLATE.md .github/ISSUE_TEMPLATE .github/ISSUE_TEMPLATE.md 2>/dev/null || true
gh issue list --state open --limit 20
gh pr list --state open --limit 20
gh issue list --state all --search "KEYWORD" --limit 10
If a template exists, use it. Reuse an issue that already covers the work. Do not duplicate.
0a. When the standard GitHub flow is mandatory
Chores may skip an issue. These use cases must not:
| Use case | Why |
|---|---|
| User asked for an issue, a PR, or "GitHub flow" | Explicit |
| Bug with repro that should outlive the branch | Durable record |
| Feature that needs acceptance criteria | Reviewable contract |
| Work spanning (or likely to span) multiple PRs | Tracker + Closes per slice |
| Other humans will review; breaking, security, or public behavior | Collaboration |
| CI, install, or shared automation | Test plan on the PR |
| An issue already covers this work | Join it; Closes #N |
Order: issue → branch → PR with Closes #N → tick boxes (0b) → grep gate (section 5) → review → gh pr checks → merge.
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.
- today First seen · 211 lines · 30 tokens per session scan A dbebb2dd07db
github-workflow is a skill published in the GitHub repository mamahoos/dot-files (4 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 2,255 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-09-04.
Other skills, from other repositories
git-commit
This skill should be used BEFORE running any git commit command. Triggers when about to run git commit. Ensures commit messages follow Conventional Commits specification and prompts for the Jira ticket number.
npm-release
Guide for setting up automated npm package releases via GitHub Actions using Trusted Publishing (OIDC). Use when creating release workflows, publishing to npm, or troubleshooting CI/CD publish failures.
gitlab-cli
Reference guide for GitLab CLI (glab) commands. Use when running glab commands for issues, merge requests, pipelines, releases, or CI/CD operations, or when the user asks about GitLab CLI syntax.
git-onboarding-auto
Git 설정부터 PR 생성까지 전 과정을 자동으로 실행합니다. "자동으로 해줘", "전부 자동화", "원클릭 PR", "자동 설정" 같은 요청에 사용됩니다.
task-snapshot
Create a commit or tag snapshot only when explicitly requested for a milestone, reproducibility checkpoint, handoff, or pinned artifact.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.