agentmods.dev

project-boards

project-boards is a skill for Claude Code, Codex from saidsef/mcp-github-pr-issue-analyser. It costs 34 tokens per session (2,292 once invoked), scanned A, original, Apache-2.0.

A GitHub Projects assistant for managing project boards. A project board is a shared view where issues and pull requests are organised by status and other fields.

In plain words
What is it for?
Use it to add issues or pull requests to boards, set their fields, inspect board contents, and remove items.
Why use it?
It removes the need to manually find board settings, add work items, and update their fields when organising repository work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 6repo changed 27d ago A scan 34 tokens original Apache-2.0

Good fit Use it to add issues or pull requests to boards, set their fields, inspect board contents, and remove items.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/saidsef/mcp-github-pr-issue-analyser/project-boards
View source ↗ saidsef/mcp-github-pr-issue-analyser
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 saidsef/mcp-github-pr-issue-analyser --skill project-boards
Clone the repo
git clone --depth 1 https://github.com/saidsef/mcp-github-pr-issue-analyser

Made for: Claude Code, Codex.

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 project-boards

README.md
[![agentmods](https://agentmods.dev/badge/skills/saidsef/mcp-github-pr-issue-analyser/project-boards/github.svg)](https://agentmods.dev/skills/saidsef/mcp-github-pr-issue-analyser/project-boards)
Your own site
<a href="https://agentmods.dev/skills/saidsef/mcp-github-pr-issue-analyser/project-boards"><img src="https://agentmods.dev/badge/skills/saidsef/mcp-github-pr-issue-analyser/project-boards/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 project-boards

Your own site · 80×15
<a href="https://agentmods.dev/skills/saidsef/mcp-github-pr-issue-analyser/project-boards"><img src="https://agentmods.dev/badge/skills/saidsef/mcp-github-pr-issue-analyser/project-boards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,292 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.
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.00034 $0.02292
Opus 5.5 $0.00014 $0.00917
Sonnet 5.5 $0.00007 $0.00458
Haiku 4.5 $0.00003 $0.00229

Measured 27d ago against content hash bf3b16bc0ce7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

project-boards 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 27d 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.

src/mcp_github/skills/project-boards/SKILL.md · 204 lines

How it starts

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

Project Boards

Read and change GitHub Projects (v2) boards: what is on one, what each card's fields say, and where an issue sits.

Prerequisites

  • project_owner, the user or organisation login that owns the board
  • project_number, which github_list_projects reports for every board the owner has. It is also the last part of the board's URL: https://github.com/users/OWNER/projects/NUMBER or https://github.com/orgs/OWNER/projects/NUMBER
  • repo_owner, repo_name and issue_number for the issue or pull request
  • A token that reaches Projects. This is a separate grant from repo: a classic token needs read:project to read and project to write, a fine-grained one needs Projects read and write

The board's owner is not always the repository's owner. An organisation board holding issues from several repositories is the common case, so read project_owner off the board URL rather than assuming it matches repo_owner.

Workflow

Finding a board

  1. Call github_list_projects with the owner's login. A person and an organisation are both served by the same call
  2. Pick the board by title and take its number. A state of closed marks a board no longer in use, so prefer an open one unless the user names it
  3. Pass the owner and number to any of the tools below

Filing an issue and placing it

  1. Call github_create_issue as usual
  2. Call github_get_project_fields to see which fields the board has and what each single-select one accepts
  3. Call github_set_project_field with the field and option names. It puts the issue on the board first if it is not already there, so github_add_to_project is only needed when no field is being set

Triaging a backlog

  1. Call github_list_project_items to read every card with its field values
  2. Group by the fields map, for example by Status, to see what is where
  3. Call github_set_project_field per issue to move it

Taking something off

  1. Call github_remove_from_project
  2. The issue stays open and untouched. Only the card goes, and the field values it held go with it
  3. Ask the user in chat before removing a card, since the field values cannot be recovered

Read the full file on GitHub · 204 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. 27d ago Changed · +33 lines · +6 tokens per session bf3b16bc0ce7
  2. 1mo ago Changed · +3 lines 1f11af97d46e
  3. 1mo ago Changed · +3 lines 153d8ad8d2d7
  4. 1mo ago First seen · 165 lines · 28 tokens per session scan A c04ea1d99cee

Subscribe to this mod's changes

project-boards is a skill published in the GitHub repository saidsef/mcp-github-pr-issue-analyser (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,292 once invoked, about $0.0001 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-08-31.

Project managementgithubmcpmcp-clientmcp-githubmcp-servermcp-tools
Related

Other skills, from other repositories

watch

Watch live IDX turnover and order books for unusual activity — value surges, auto-reject approach, one-sided depth, walls appearing or withdrawn, quiet stocks waking up, UMA flags — plus delayed print-by-print attribution and end-of-day broker context. Use when the user runs /watch, or asks what is trading right now…

INo-xious/stockbit-mcp · 88 tokens

stockbit-status

Check whether the Stockbit session is still valid — main session expiry, whether trading credentials are stored, and the current trading mode. Use when the user asks "am I still logged in to Stockbit", "has my session expired", "is trading on", or when a stockbit MCP tool starts failing with an auth error.

INo-xious/stockbit-mcp · 70 tokens

stockbit-auth

Log in to Stockbit and capture the session for this server — opens the browser login flow and verifies the token was stored. Use when the user asks to log in or re-authenticate to Stockbit, or after a status check reports the session expired, HTTP 401, or logged out.

INo-xious/stockbit-mcp · 63 tokens

bandar-check

Answer "who is accumulating this stock?" for an IDX ticker using Stockbit broker-flow data. Use when the user asks about bandar, big money, accumulation, distribution, foreign flow, asing, or who is on the other side of the tape.

INo-xious/stockbit-mcp · 54 tokens

chart-markup

Read and draw on the user's own Stockbit chart — levels, trend lines, studies, screenshots and saving the layout. Use when the user asks to draw, mark up, annotate or look at their chart.

INo-xious/stockbit-mcp · 46 tokens

stock-deep-dive

Work through one IDX symbol properly — trend, patterns, timeframe alignment, fundamentals and broker flow — and present a lean with its evidence. Use when the user asks what you think of a stock, or to look at, research or analyse one.

INo-xious/stockbit-mcp · 55 tokens