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 DominikTobureto/awesome-grok-build --skill git-github-flowgit clone --depth 1 https://github.com/DominikTobureto/awesome-grok-buildWrote 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/dominiktobureto/awesome-grok-build/git-github-flow)<a href="https://agentmods.dev/skills/dominiktobureto/awesome-grok-build/git-github-flow"><img src="https://agentmods.dev/badge/skills/dominiktobureto/awesome-grok-build/git-github-flow.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.00398 |
| Opus 5 | $0.00020 | $0.00199 |
| Sonnet 5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
git-github-flow 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 8d 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
Git GitHub Flow
Turn local changes into a clean, reviewable contribution.
Grok Build Mode
- Use Plan Mode before rewriting commits, rebasing, force-pushing, or touching release branches.
- Use subagents for merge readiness:
diff: changed files and intent.tests: verification status and gaps.docs: README/changelog/release notes.risk: risky files, migrations, auth, config.
- Arena-style PR description: generate 2-3 PR narratives and choose the clearest.
- Human-in-the-loop: never push, force-push, publish, or merge without explicit user approval.
Workflow
- Inspect
git status, branch, remotes, and recent commits. - Separate unrelated changes.
- Stage intentionally.
- Write a concise commit message:
- imperative subject;
- why in body when useful;
- tests run.
- Draft PR description with:
- summary;
- screenshots/demo if relevant;
- verification;
- risks;
- follow-ups.
- Push only after approval.
GitHub Best Practices
- Link issues when known.
- Keep PRs small and coherent.
- Do not include secrets or local config.
- Do not mark generated files for review unless necessary.
- Address review comments with targeted commits.
Example Prompts
Use git-github-flow. Prepare a clean commit and PR description from my current diff. Do not push yet.
Use git-github-flow to respond to PR review comments. Preserve unrelated user changes.
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.
- 8d ago First seen · 57 lines · 41 tokens per session scan A ba2185869c54
git-github-flow is a skill published in the GitHub repository DominikTobureto/awesome-grok-build (60 stars, last pushed 15d ago), licensed MIT. It adds 41 tokens to every session and 398 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
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.