github-project-menu.template

A workflow for viewing and synchronising a GitHub Project board, where a team organises issues and tracks their status.

In plain words
What is it for?
Use it to inspect the board and sync its progress using the configured repository and project details.
Why use it?
It gives a current view of board items and helps keep project progress aligned with the repository.

Command

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 commands/evan043/claude-cli-advanced-starter-pack/github-project-menu.template
Clone the repo
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-pack
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 561 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.00000 $0.00561
Opus 5 $0.00000 $0.00280
Sonnet 5 $0.00000 $0.00112
Haiku 4.5 $0.00000 $0.00056

Measured 2d ago against content hash c2b4f3deca56, 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-menu.template 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.

templates/commands/github-project-menu.template.md · 80 lines

How it starts

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

Codex Runtime Compatibility

This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:

  • AskUserQuestion => ask the user directly in chat.
  • WebSearch/WebFetch => use available web tools (search_query, open, find) and cite links.
  • Read/Write => use shell/filesystem tools in this workspace.
  • Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
  • Keep intent and output format identical; only adapt execution mechanics.

description: View and sync GitHub Project Board status model: haiku

/github-project-menu - GitHub Project Board Sync

View current status of your GitHub Project Board and sync progress.

{{#if versionControl.projectBoard.number}}

Project Board Configuration

Setting Value
Owner {{versionControl.owner}}
Repository {{versionControl.repo}}
Project # {{versionControl.projectBoard.number}}
URL {{versionControl.projectBoard.url}}

Commands

View Board Status

# View all items on the project board
gh project item-list {{versionControl.projectBoard.number}} --owner {{versionControl.owner}} --format json | jq '.items'

# View issues only
gh issue list --repo {{versionControl.owner}}/{{versionControl.repo}} --state open --json number,title,state,labels

# View PRs
gh pr list --repo {{versionControl.owner}}/{{versionControl.repo}} --state open --json number,title,state,headRefName

Sync Tasks

  1. Pull from GitHub - Fetch latest status from Project Board
  2. Push to GitHub - Update Project Board with local progress
  3. Reconcile - Two-way sync with conflict resolution

Instructions for Claude

When this command is invoked:

  1. Check gh CLI authentication: gh auth status
  2. Fetch current board status using the commands above
  3. Display a formatted summary:
    • Total items
    • Items by status (Todo, In Progress, Done)
    • Recent activity
  4. Ask if user wants to sync or view details

Read the full file on GitHub · 80 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 · 80 lines · 0 tokens per session scan A c2b4f3deca56

Subscribe to this mod's changes

github-project-menu.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 561 tokens. 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.