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.
npx skills add bks-lab/open-bridge --skill github-projects-managergit clone --depth 1 https://github.com/bks-lab/open-bridgeWrote 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/bks-lab/open-bridge/github-projects-manager)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/github-projects-manager"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/github-projects-manager/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/bks-lab/open-bridge/github-projects-manager"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/github-projects-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.04277 |
| Opus 5.5 | $0.00035 | $0.01711 |
| Sonnet 5.5 | $0.00017 | $0.00855 |
| Haiku 4.5 | $0.00009 | $0.00428 |
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 16d 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.
How it starts
The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Projects Manager
Execution and governance layer for GitHub Projects V2. This skill runs the
actual CLI and GraphQL commands, and it decides when a write is allowed: the
K/W/B governance rules, the board health checks (R1 to R7) and the setup of a
new board live in references/governance.md and references/setup.md.
Decision tree
User intent?
├─ "Create issue" / "Track this" → Issue Creation (below) + governance.md K rules
├─ "Set field" / "Set status" → Field Updates (below); into review → governance.md § Review comment
├─ "Show board" / "What's active?" → Board query (graphql-patterns.md § Board Query)
├─ "Audit board" / "Reconcile" → Board Hygiene (below), scripts/board-audit.sh
├─ "Board health" / "Governance" → references/governance.md (R1 to R7)
├─ "Convert drafts to issues" → references/governance.md § Draft to issue conversion
├─ "Set up a project" / new board → references/setup.md
└─ Change fields or options → Field Schema Operations (below), human gate
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, keeping their field values
- Checking governance and board health (R1 to R7) and setting up new boards
- 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
- Identify the target project (from caller context, issue URL, or
#number) - Read
workflow/projects/{slug}.yamlfor field values, governance rules, and state mappings - If a bound context exists (e.g.
workflow/contexts/customer-a.yaml), readproject_custom_fieldsfor field-specific overrides and readonly field lists
What ships with it
5 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.
- 16d ago Changed · +10 lines f800baba597a
- 22d ago Changed · +112 lines · -81 tokens per session a02d901f5ef6
- 1mo ago First seen · 221 lines · 168 tokens per session scan A 282d00fde8e1
github-projects-manager is a skill published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 4,277 once invoked, about $0.0003 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.
Other skills, from other repositories
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
paperclip-board
Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
paperclip-distill
Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.
summarize-status
Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.