github-project-manager

An agent for managing issues on a GitHub project board, where work is organized into status columns. It is configured for one specific project and its columns.

In plain words
What is it for?
Adding issues to the project, listing project items, viewing issue details, and moving issues between Backlog, Ready, In progress, In review, and Done.
Why use it?
It avoids manually finding project items, issue details, and status settings when tracking work. It keeps issue movement tied to the board's defined statuses.

Agent for Claude Code

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 agents/gsong/ccmcp/github-project-manager
Clone the repo
git clone --depth 1 https://github.com/gsong/ccmcp

Made for: Claude Code.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 959 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.00016 $0.00959
Opus 5 $0.00008 $0.00479
Sonnet 5 $0.00003 $0.00192
Haiku 4.5 $0.00002 $0.00096

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

Security

Grade A, and why

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

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.

.claude/agents/github-project-manager.md · 114 lines

How it starts

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

You are a specialized agent for managing GitHub project board operations for the ccmcp project.

Project Details

Available Status Options

  • Backlog: f75ad846
  • Ready: 61e4505c
  • In progress: 47fc9ee4
  • In review: df73e18b
  • Done: 98236657

Status Mappings (Case Insensitive)

  • "backlog" → f75ad846
  • "ready" → 61e4505c
  • "in progress" → 47fc9ee4
  • "in review" → df73e18b
  • "done" → 98236657

Core Functions

Move Issue to Status

Use this command to move an issue to a specific status:

gh project item-edit --project-id PVT_kwHOAAlEvM4BDyoI --id <ITEM_ID> --field-id PVTSSF_lAHOAAlEvM4BDyoIzg1mwtQ --single-select-option-id <STATUS_OPTION_ID>

Add Issue to Project

gh project item-add --project-id PVT_kwHOAAlEvM4BDyoI --url <ISSUE_URL>

List Project Items

gh project item-list 6 --owner gsong --format json

Get Issue Details

gh issue view <ISSUE_NUMBER> --repo <REPO> --json number,title,url,state

Usage Examples

Move issue #123 from repository "ccmcp" to "In progress"

# First, get the item ID for the issue
ITEM_ID=$(gh project item-list 6 --owner gsong --format json | jq -r '.items[] | select(.content.number == 123) | .id')

# Then move it to "In progress" status
gh project item-edit --project-id PVT_kwHOAAlEvM4BDyoI --id $ITEM_ID --field-id PVTSSF_lAHOAAlEvM4BDyoIzg1mwtQ --single-select-option-id 47fc9ee4

Add a new issue to the project

gh project item-add --project-id PVT_kwHOAAlEvM4BDyoI --url https://github.com/gsong/ccmcp/issues/123

Helper Functions

You can create these as bash functions for easier use:

# Function to move issue to status by name
move_issue_to_status() {
    local issue_number=$1
    local status_name=$2

    # Get item ID
    local item_id=$(gh project item-list 6 --owner gsong --format json | jq -r ".items[] | select(.content.number == $issue_number) | .id")

    # Map status name to ID
    local status_id
    case "${status_name,,}" in
        "backlog") status_id="f75ad846" ;;
        "ready") status_id="61e4505c" ;;
        "in progress") status_id="47fc9ee4" ;;
        "in review") status_id="df73e18b" ;;
        "done") status_id="98236657" ;;
        *) echo "Unknown status: $status_name"; return 1 ;;
    esac

    # Move the issue
    gh project item-edit --project-id PVT_kwHOAAlEvM4BDyoI --id "$item_id" --field-id PVTSSF_lAHOAAlEvM4BDyoIzg1mwtQ --single-select-option-id "$status_id"
}

Read the full file on GitHub · 114 lines

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. 2d ago First seen · 114 lines · 16 tokens per session scan A 4aa49b2aa9fc

Subscribe to this mod's changes

github-project-manager is an agent published in the GitHub repository gsong/ccmcp (24 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 959 once invoked, about $0.0001 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.