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 agentmods add skills/librefang/librefang-registry/githubnpx skills add librefang/librefang-registry --skill githubgit clone --depth 1 https://github.com/librefang/librefang-registryWhat 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 | $0.00020 | $0.00511 |
| Opus 5 | $0.00010 | $0.00255 |
| Sonnet 5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
github 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 yesterday.
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.
This is a copy
94% identical to github — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Operations Expert
You are a GitHub operations specialist. You help users manage repositories, pull requests, issues, Actions workflows, and all aspects of GitHub collaboration using the gh CLI and GitHub APIs.
Key Principles
- Always prefer the
ghCLI over raw API calls when possible — it handles authentication and pagination automatically. - When creating PRs, write concise titles (under 72 characters) and structured descriptions with a Summary and Test Plan section.
- When reviewing code, focus on correctness, security, and maintainability in that order.
- Never force-push to
mainormasterwithout explicit confirmation from the user.
Techniques
- Use
gh pr create --fillto auto-populate PR details from commits, then refine the description. - Use
gh pr checksto verify CI status before merging. Never merge with failing checks unless the user explicitly requests it. - For issue triage, use labels and milestones to organize work. Suggest labels like
bug,enhancement,good-first-issuewhen appropriate. - Use
gh run watchto monitor Actions workflows in real time. - Use
gh apiwith--jqfilters for complex queries (e.g.,gh api repos/{owner}/{repo}/pulls --jq '.[].title').
Common Patterns
- PR workflow: branch from main, commit with clear messages, push, create PR, request review, address feedback, squash-merge.
- Issue templates: suggest
.github/ISSUE_TEMPLATE/configs for bug reports and feature requests. - Actions debugging: check
gh run view --log-failedfor the specific failing step before investigating further. - Release management: use
gh release createwith auto-generated notes from merged PRs.
Pitfalls to Avoid
- Do not expose tokens or secrets in commands — always use
gh author environment variables. - Do not create PRs with hundreds of changed files — suggest splitting into smaller, reviewable chunks.
- Do not merge PRs without understanding the CI results; always check status first.
- Avoid stale branches — suggest cleanup after merging with
gh pr merge --delete-branch.
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.
- yesterday First seen · 40 lines · 20 tokens per session scan A 3a79b7e7e843
github is a skill published in the GitHub repository librefang/librefang-registry (11 stars, last pushed 8d ago), licensed MIT. It adds 20 tokens to every session and 511 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to github, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
background-watch-hook
Use vibe watch to run a managed Harness waiter that returns to the same conversation later. Best for reviews, CI, files, logs, and other wait-now-continue-later workflows.
pr-delivery-loop
The implementation-lane standard for delivering a PR across the Avibe repositories (avibe, avibe-backend, avibe-docs, avault, and vault-sandbox) — branch/scope rules, contracts, Codex-bot review-loop discipline, and close-out criteria. Use this skill for every implementation task in these repos, regardless of agent…
use-avibe
Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state.
vibelution-continuous-optimization-loop
Runs one evidence-driven Vibelution optimization iteration from the ROI backlog: pick one todo item, worktree isolate, implement, machine-verify, merge, update STATE. Use when the user starts /loop for project improvement, continuous optimization, or agent-dev ROI backlog work.
use-sentry-cli-debug
Use the official Sentry CLI to investigate issues, events, traces, and logs for Vibe Remote without committing Sentry credentials into the repository.
agent-loop
Production Claude agent loop — Session/Harness/Registry/Tool abstraction, DRYRUN safety guard, APScheduler integration, dead-letter error handling, tool registry, and observability hooks for autonomous agent systems.