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 J-StaR-Films-Studios/VibeCode-Protocol-Suite --skill github-opsgit clone --depth 1 https://github.com/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/j-star-films-studios/vibecode-protocol-suite/github-ops)<a href="https://agentmods.dev/skills/j-star-films-studios/vibecode-protocol-suite/github-ops"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/github-ops/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/j-star-films-studios/vibecode-protocol-suite/github-ops"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/github-ops.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.00025 | $0.01749 |
| Opus 5 | $0.00013 | $0.00874 |
| Sonnet 5 | $0.00005 | $0.00350 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
github-ops 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 7d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Ops Skill
Complete GitHub automation toolkit using the gh CLI. Covers issue management, project boards, label systems, and bulk operations.
When to Use
- User mentions "GitHub issues", "project board", or "gh cli"
- Setting up automation for a new repo
- Bulk-creating issues from markdown specs
- Managing GitHub Projects (v2)
Prerequisites
# Install GitHub CLI
winget install GitHub.cli # Windows
brew install gh # macOS
# Authenticate
gh auth login
# Verify
gh auth status
1. Bulk Issue Sync (publish_issues.ps1)
Location: $env:USERPROFILE\.gemini\antigravity\skills\github-ops\scripts\publish_issues.ps1
[!TIP] The script auto-detects the repository from the current working directory. Just
cdto your project folder before running.
Features
| Feature | Description |
|---|---|
| Smart Sync | Only processes files that changed since last run (uses .issue-sync-state.json) |
| Auto-Close | Closes issue when all checkboxes (- [x]) are ticked |
| Auto-Archive | Moves completed .md files to closed/ subfolder |
| Natural Sort | Processes Issue_1, Issue_2... Issue_10 (not 1, 10, 11) |
| Date Sync | Sets Start/Target dates on GitHub Projects |
Required Flags
| Flag | Required? | Description |
|---|---|---|
| (none) | - | Creates new issues only (skips existing) |
-Update |
For sync | Updates existing issues |
-AutoArchive |
Optional | Moves completed issues to closed/ folder |
-DryRun |
Optional | Preview mode - no changes made |
-Force |
Optional | Bypass change detection, sync all files |
Project Date Sync Flags (ALL required with -SyncDates)
| Flag | Description | How to Get |
|---|---|---|
-SyncDates |
Enable date sync | Just add the flag |
-ProjectNumber |
Project board number | gh project list --owner USERNAME |
-ProjectId |
Project node ID | See below |
-StartDateFieldId |
Start Date field ID | See below |
-TargetDateFieldId |
Target Date field ID | See below |
What ships with it
3 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.
- 7d ago First seen · 221 lines · 25 tokens per session scan A e12331a81dda
github-ops is a skill published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed today), licensed ISC. It adds 25 tokens to every session and 1,749 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-09-03.
Other skills, from other repositories
missive
Invoke only when spawning a quest from a GitHub issue reference. Fetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.