Borrowing it
Nothing to install: this file belongs to iBrain-BVBA/gutt-claude-code-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/iBrain-BVBA/gutt-claude-code-plugin/main/.claude/skills/github-workflow/SKILL.mdgit clone --depth 1 https://github.com/iBrain-BVBA/gutt-claude-code-pluginWrote 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/ibrain-bvba/gutt-claude-code-plugin/github-workflow)<a href="https://agentmods.dev/skills/ibrain-bvba/gutt-claude-code-plugin/github-workflow"><img src="https://agentmods.dev/badge/skills/ibrain-bvba/gutt-claude-code-plugin/github-workflow/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/ibrain-bvba/gutt-claude-code-plugin/github-workflow"><img src="https://agentmods.dev/badge/skills/ibrain-bvba/gutt-claude-code-plugin/github-workflow.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.00116 | $0.01655 |
| Opus 5.5 | $0.00046 | $0.00662 |
| Sonnet 5.5 | $0.00023 | $0.00331 |
| Haiku 4.5 | $0.00012 | $0.00166 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflow
Announce: "Following gutt GitHub workflow..."
The Rule
All code changes go through PRs with Copilot review. This is the quality gate — Copilot reviews every PR and does one last iteration before the code lands.
Committing to feature branches is fine and expected. What's not allowed is pushing directly to the default branch or merging without Copilot review.
Which toolchain — check, don't assume
Two paths exist and most sessions have only one of them. Establish which before you plan the delivery, not after you've announced a sequence you can't run:
- GitHub MCP (
mcp__github__*) — present in Cowork and in sessions with the GitHub MCP server connected. Probe with ToolSearch; do not assume it from the fact that this skill names those tools. ghCLI + localgit— the path in a normal Claude Code terminal session, wheremcp__github__*tools are typically absent. Verify once withgh auth status.
The rules below are toolchain-independent. Tool names are given for both.
What You Can and Can't Do
Go ahead:
- Create branches (
mcp__github__create_branch/git checkout -b) - Commit to feature branches (
mcp__github__push_files,mcp__github__create_or_update_file/git commit+git push -u origin <branch>) - Create PRs (
mcp__github__create_pull_request/gh pr create --base <base> --head <branch>) - Request Copilot review (
mcp__github__request_copilot_review/ see theghrecipe below) - Read anything — files, commits, diffs, PRs, issues
- Search code, issues, PRs
- Create/update issues
- Update PR metadata
Always ask the user first:
- Merging PRs (
mcp__github__merge_pull_request) — the user or Copilot workflow handles this
Never do:
- Push directly to
main - Merge without Copilot having reviewed
Standard Workflow
When delivering code to GitHub, follow this sequence:
- Pick the base branch deliberately — see below. It is not automatically the default branch.
- Create a feature branch from that base
- Push your code to the feature branch
- Create a PR against the same base, with a clear title referencing any Jira ticket, and a body describing what changed and why
- Request Copilot review immediately after PR creation
- Stop — let Copilot review and the user decide when to 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.
- 1mo ago First seen · 120 lines · 116 tokens per session scan A afd91e97950b
github-workflow is a skill published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 116 tokens to every session and 1,655 once invoked, about $0.0005 per session on Opus 5.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-31.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.