Borrowing it
Nothing to install: this file belongs to guillermoscript/lms-front. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/guillermoscript/lms-front/master/.agents/skills/gh-board/SKILL.mdgit clone --depth 1 https://github.com/guillermoscript/lms-frontWrote 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.
[](https://agentmods.dev/skills/guillermoscript/lms-front/gh-board)<a href="https://agentmods.dev/skills/guillermoscript/lms-front/gh-board"><img src="https://agentmods.dev/badge/skills/guillermoscript/lms-front/gh-board/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.
<a href="https://agentmods.dev/skills/guillermoscript/lms-front/gh-board"><img src="https://agentmods.dev/badge/skills/guillermoscript/lms-front/gh-board.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00061 | $0.01480 |
| Opus 5.5 | $0.00024 | $0.00592 |
| Sonnet 5.5 | $0.00012 | $0.00296 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade B, and why
gh-board 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
description: Operate any GitHub Projects (v2) board by name — add issues/PRs, find existing items, set Status/Priority/Size or any single-select field — without hardcoding field or option IDs. Use whenever the user asks How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GH Board — GitHub Projects (v2) operations by name
Everything here is backed by the bundled scripts/board.sh, which resolves
field and option IDs by name at call time via gh project field-list —
nothing is hardcoded to a specific board, so it works against any Projects v2
board. The script is bundled with this skill (not the target repo): invoke it
by the skill's own path, <skill-dir>/scripts/board.sh, where <skill-dir>
is wherever this SKILL.md was loaded from.
Preconditions
The script needs two env vars on every call:
GH_PROJECT_OWNER=<github-org-or-user> GH_PROJECT_NUMBER=<number>
Resolve them in this order:
- Already known in this session — use them.
- The repo's workflow config:
.claude/gh-workflow.config.json, keyprojectBoard: { "owner": ..., "number": ... }. Read it via thegh-repo-configskill'sconfig.sh get .projectBoard(or plainjqif that skill isn't loaded). - Discover:
gh project list --owner <org-from-repo> --format json— if exactly one open project plausibly covers this repo, propose it to the user. If none or ambiguous, ask which board (owner + number), and offer to save the answer to the config so it's never asked again.
If the user says there is no board, or none can be found, board operations are simply skipped — that's an expected state, not a failure.
Commands
board.sh add <issue-or-pr-url> Add to board (idempotent), prints item id
board.sh find <owner/repo> <number> Print item id for issue/PR #N; empty if absent
board.sh set-field <item-id> <field> <opt> Set any single-select field by name
board.sh get-field <item-id> <field> Read an item's current value; empty if unset
board.sh status <item-id> <name> Shorthand: set-field ... Status <name>
board.sh priority <item-id> <name> Shorthand: set-field ... Priority <name>
board.sh size <item-id> <name> Shorthand: set-field ... Size <name>
board.sh has-field <field-name> Exit 0 if the board has this field
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.
- 1mo ago First seen · 125 lines · 61 tokens per session scan B 1fb0916bd3d2
gh-board is a skill published in the GitHub repository guillermoscript/lms-front (40 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 1,480 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
summarize-activity
Summarize engineering activity in classroomio/classroomio between two dates — merged PRs, still-open PRs opened in that window, and their demo videos — into a markdown report. Use when the user asks what shipped, what happened, or for a summary/recap/digest of engineering work over a date range.
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
linear-app-setup
Create and configure a Linear agent app so the assistant can manage issues, projects, and workflows under its own identity.
agent-phase-closeout
A Chinese-language process for closing out a completed work stage and recording its state. It summarizes finished work, preserves decisions, freezes completed interfaces, and writes a resume checkpoint.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.