github-projects-manager

A tool for managing GitHub Projects V2 boards, which organise issues and work into statuses and custom fields.

In plain words
What is it for?
Use it to create issues, add them to boards, update fields, move many items between statuses, query board data, convert drafts, and audit board hygiene.
Why use it?
It keeps GitHub issues and project-board records aligned, reducing manual updates and making missing or inconsistent board items easier to find.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/bks-lab/open-bridge/github-projects-manager
Any agent
npx skills add bks-lab/open-bridge --skill github-projects-manager
Clone the repo
git clone --depth 1 https://github.com/bks-lab/open-bridge

Made for: Claude Code, Codex.

Per session 168 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,316 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00168 $0.02316
Opus 5 $0.00084 $0.01158
Sonnet 5 $0.00034 $0.00463
Haiku 4.5 $0.00017 $0.00232

Measured 3d ago against content hash 282d00fde8e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-projects-manager 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 3d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/board-audit.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/github-projects-manager/SKILL.md · 221 lines

How it starts

The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Projects Manager

Execution layer for GitHub Projects V2 operations. The project-advisor skill handles governance and decision-making; this skill handles the actual CLI and GraphQL commands.

When to use

  • Creating issues and adding them to project boards
  • Setting or updating custom project fields (Status, Priority, Billing Scope, Approval, Root Cause, Person Days, etc.)
  • Batch field transitions (e.g. "set Approval to Submitted on 16 items")
  • Querying board state (items by status, field counts, stale items)
  • Converting drafts to issues
  • Auditing board hygiene — coverage (open issues that never made it onto the board) and reconciliation (board Status disagreeing with the issue's real state / close-reason). See Board Hygiene below.

Loading sequence

  1. Identify the target project (from caller context, issue URL, or #number)
  2. Read workflow/projects/{slug}.yaml for field values, governance rules, and state mappings
  3. If a bound context exists (e.g. workflow/contexts/customer-a.yaml), read project_custom_fields for field-specific overrides and readonly field lists

Issue Creation (3-step atomic)

Every issue creation follows this exact sequence — no shortcuts:

Step 1: gh issue create --repo {org}/{issue_repo} --title --body --label
Step 2: gh project item-add {number} --owner {org} --url {issue_url}
Step 3: Verify — confirm the item appears on the board

After creation, immediately classify with at minimum:

  • Status (from project config default)
  • All billing fields if the project has them (Billing Scope, Root Cause, Approval)

Connectedness is not optional. An issue that exists but is not on the board is invisible to everyone who works from the board. Step 2 + 3 are mandatory — never gh issue create without adding to the project and confirming it landed. The same applies when you touch an existing issue for this project: if it is not on the board, add it. Periodically verify the whole set with the coverage audit (Board Hygiene below) — orphaned issues are a silent failure mode.

Read the full file on GitHub · 221 lines

Files

What ships with it

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

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. 3d ago First seen · 221 lines · 168 tokens per session scan A 282d00fde8e1

Subscribe to this mod's changes

github-projects-manager is a skill published in the GitHub repository bks-lab/open-bridge (8 stars, last pushed 3d ago), licensed MIT. It adds 168 tokens to every session and 2,316 once invoked, about $0.0008 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-31.

Related

Other skills, from other repositories

xlsx

Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify…

AminulIslamSifat/Sable · 96 tokens

pdf

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

AminulIslamSifat/Sable · 50 tokens

pptx

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks.

AminulIslamSifat/Sable · 62 tokens

docx

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4)…

AminulIslamSifat/Sable · 77 tokens

process-builder

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

a5c-ai/babysitter · 32 tokens

retrospect-external-babysitter-run

For a repository in the babysitter-users catalog, locate its babysitter processes and any committed runs (.a5c/runs/ /) and perform a retrospective on a chosen run -- what went well, what failed, process suggestions, quality of effect design, breakpoint patterns -- mirroring the /babysitter:retrospect workflow but…

a5c-ai/babysitter · 120 tokens