agentmods.dev

github-cli-workflow

github-cli-workflow is a skill for Claude Code from ulises-jeremias/agent-toolkit. It costs 43 tokens per session (521 once invoked), scanned A, original, MIT.

A GitHub command-line workflow for pushing a branch and opening a draft pull request with a title and description from a template or file.

In plain words
What is it for?
It helps publish a branch, prepare a pull-request body, create a draft pull request, and save the description for human review if needed.
Why use it?
It removes repetitive pull-request setup and helps keep descriptions consistent with the repository's review format.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the agent-toolkit-complete plugin — 106 skills shipped together

not rated 19repo yesterday A scan SkillSpector: pass 43 tokens original MIT

Good fit It helps publish a branch, prepare a pull-request body, create a draft pull request, and save the description for human review if needed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ulises-jeremias/agent-toolkit/github-cli-workflow
View source ↗ ulises-jeremias/agent-toolkit agent-toolkit.io
Install

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.

Any agent
npx skills add ulises-jeremias/agent-toolkit --skill github-cli-workflow
Clone the repo
git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkit

Made for: Claude Code.

Or install agent-toolkit-complete, the plugin that ships this one along with the rest of its 106 skills.

Wrote 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.

agentmods badge for github-cli-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/github-cli-workflow/github.svg)](https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/github-cli-workflow)
Your own site
<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/github-cli-workflow"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/github-cli-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.

agentmods 80×15 button for github-cli-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/github-cli-workflow"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/github-cli-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 521 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.00521
Opus 5.5 $0.00017 $0.00208
Sonnet 5.5 $0.00009 $0.00104
Haiku 4.5 $0.00004 $0.00052

Measured 1mo ago against content hash 618084f066f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

github-cli-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.

plugins/agent-toolkit-complete/.github/skills/github-cli-workflow/SKILL.md · 50 lines

What it actually says

GitHub CLI — draft PR (HOW)

Use this skill when the remote is GitHub and you need to push and open a draft pull request. Workflow skills delegate here; this skill does not replace Jira or ClickUp procedures.

Prerequisites

  • gh authenticated (gh auth status).
  • Branch pushed to origin (or the remote your team uses).
  1. Ensure the working branch tracks the remote: push with upstream as usual for the repo.
  2. Prefer the repository PR template for the body: use --body-file pointing at a generated file that includes template sections, or paste from .github/pull_request_template.md when required. If no template exists in the repo, use pr-fallback (WHAT) to build the body and output-handshake to confirm where the file lives and that a human will review before gh pr create.
  3. Create a draft PR:
gh pr create --draft --title "YOUR_TITLE" --body-file /path/to/body.md

If the repo expects a base branch other than the default:

gh pr create --draft --base develop --title "YOUR_TITLE" --body-file /path/to/body.md
  1. If --draft is rejected by gh, retry once without --draft and state in chat that the PR could not be created as draft via CLI.

Title and body

  • Keep titles within team conventions (often including ticket keys).
  • Validate title and body with the user before calling the step complete.

Fallback (CLI failure)

  1. Write an untracked file PR_DESCRIPTION_<WORK_ITEM_ID>.md in the repo root or /tmp with title + body ready to paste.
  2. Do not git add this file.
  3. Give manual steps: open the compare URL on GitHub and create a draft PR from the branch, pasting from the file.

Safety

  • Do not expose tokens or paste secrets into PR bodies.
  • Do not force-push shared default branches unless the user explicitly requests it.
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.

  1. 1mo ago First seen · 50 lines · 43 tokens per session scan A 618084f066f5

Subscribe to this mod's changes

github-cli-workflow is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 521 once invoked, about $0.0002 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-09-04.

Claude CodeGit and workflowagent-toolkitai-agentsai-toolscursorgithub-copilot
Related

Other skills, from other repositories

github-navigator

GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any github.com URL or GitHub repo path like owner/repo. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR'…

arvindand/agent-skills · 107 tokens

active-review

Use when the user wants to prepare for a manual PR code review and asks for help targeting it — a terse PR summary, ranked files to read first, and paste-ready inline comment drafts with GitHub deep-links. Triggers: "active review this PR", "walk me through this PR", "help me review this", "give me inline comments to…

paultyng/skill-issue · 0 tokens

analyze-knowledge

Use when the user asks who knows specific code, who should review a PR or files, what the lottery factor is, whether knowledge is concentrated or spread, who to talk to about a code area, or when suggesting reviewers beyond GitHub's built-in suggestions.

paultyng/skill-issue · 57 tokens

bisect

Use when hunting a regression, phrases like "bisect", "find the commit that broke X", "this used to work", "regression in test Y", "when did start". Also use when escalated from ci-debug-loop because log analysis can't pinpoint the offending change, or when a previously-passing test/build/behavior is now failing and…

paultyng/skill-issue · 121 tokens

fix-pr-conflict

Resolve merge conflicts on a pull request by rebasing onto the base branch. Use when a PR is not mergeable, has merge conflicts, or the user asks to fix conflicts on a PR.

paultyng/skill-issue · 44 tokens

create-pr

Use when creating a new GitHub pull request, opening a PR for the current branch, or when another skill (like ship-it) needs a PR created for a branch that does not have one yet.

paultyng/skill-issue · 44 tokens