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/bodangren/git-workflow/issue-executornpx skills add bodangren/git-workflow --skill issue-executorgit clone --depth 1 https://github.com/bodangren/git-workflowWhat 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.00061 | $0.01254 |
| Opus 5 | $0.00030 | $0.00627 |
| Sonnet 5 | $0.00012 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade B, and why
issue-executor scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
**Solution**: Install the required tool. For `jq`, use `sudo apt install jq` or `brew install jq`. For `gemini`, follow its official installation instructions. How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Executor
Purpose
To kickstart the development workflow for a single GitHub issue by generating a comprehensive, context-aware implementation plan. This skill leverages the Gemini CLI to synthesize issue details, relevant specifications, and historical learnings from the project retrospective into a clear, actionable plan. It then creates an isolated feature branch, setting the stage for focused, spec-driven development.
When to Use
Use this skill in the following situations:
- Starting work on a planned GitHub issue from the current sprint.
- Beginning a work session and wanting a synthesized plan before coding.
- Needing to load and understand all context for an issue efficiently.
Prerequisites
- GitHub repository with issues created (via sprint-planner skill).
- Git working directory is clean (no uncommitted changes).
- Currently on the
mainbranch. ghCLI tool installed and authenticated.jqtool installed for JSON parsing.geminiCLI tool installed and authenticated.- Project has a
docs/structure with specs and aRETROSPECTIVE.md.
Core Principles
Context is King
Instead of just viewing files, the skill synthesizes all relevant context into a coherent plan:
- Issue details: Requirements and acceptance criteria.
- Spec files: All specifications referenced in the issue.
- Retrospective: Learnings from past work to avoid repeating mistakes.
Isolation
All work happens on a dedicated feature branch to:
- Protect the
mainbranch from work-in-progress. - Enable a clean Pull Request workflow.
- Allow abandoning work without impacting the main codebase.
Atomic Work
Each issue represents a single, well-defined task that can be completed and reviewed as a unit.
Workflow
Step 1: Identify the Issue
Determine which issue to work on. The user specifies the issue number (e.g., #45).
Step 2: Run the Helper Script
Execute the work-on-issue.sh script with the issue number:
bash scripts/work-on-issue.sh 45
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 123 lines · 61 tokens per session scan B 756a19ea009c
issue-executor is a skill published in the GitHub repository bodangren/git-workflow (11 stars, last pushed 8mo ago), licensed MIT. It adds 61 tokens to every session and 1,254 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.