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/alirezasoltanijazi/skillnir/githubnpx skills add AlirezaSoltaniJazi/Skillnir --skill githubgit clone --depth 1 https://github.com/AlirezaSoltaniJazi/SkillnirWhat 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.00128 | $0.02680 |
| Opus 5 | $0.00064 | $0.01340 |
| Sonnet 5 | $0.00026 | $0.00536 |
| Haiku 4.5 | $0.00013 | $0.00268 |
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 2d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before You Start
Read LEARNED.md first. It holds corrections, preferences, and per-repo conventions (branch style, base branch, PR-template path, label taxonomy, the linked Jira review status) discovered in previous sessions. Every rule there overrides defaults in this skill.
Announce skill usage. Say "Using: github skill" at the very start of your response before doing any work.
Preflight: run gh auth status. Note the token's scopes — if it lacks project, never pass gh pr create -p (adding a PR to a GitHub Project needs that scope).
When to Use
- Raising a pull request following the repo's convention
- Creating a convention-named branch for a Jira ticket
- Committing with the repo's ticket-prefixed subject format
- Building a PR body from the diff + the repo's PR template
- Applying labels / milestone and updating the linked Jira ticket
Do NOT Use
- GitLab merge requests — use gitlab.
- Creating or transitioning Jira tickets as the primary task — use jira. This skill only updates the linked ticket at the end of the PR flow.
- CI/CD workflow files (
.github/workflows/), pre-commit, quality gates — use devopsEngineer. - Never add file paths / code to the Jira ticket — keep the ticket non-technical; technical detail goes in the PR body.
Access & Convention Detection
| Fact | Value |
|---|---|
| Tool | gh CLI (authenticated) + git |
| Owner / repo | Auto-resolved from the current repo — never hardcode |
| Default branch | Detect, don't assume |
| Token scopes | From gh auth status — no project ⇒ never gh pr create -p |
What ships with it
9 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.
- INJECT.md 729 B
- LEARNED.md 648 B
- references/ai-interaction-guide.md 6.3 KB
- references/branch-naming.md 3.9 KB
- references/commit-conventions.md 4.7 KB
- references/labels-and-milestones.md 4.1 KB
- references/pr-recipes.md 5.7 KB
- references/pr-templates.md 7.4 KB
- scripts/validate-github.sh 931 B runs code
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.
- 2d ago First seen · 139 lines · 128 tokens per session scan A 1796b25610c3
github is a skill published in the GitHub repository AlirezaSoltaniJazi/Skillnir (7 stars, last pushed 1mo ago), licensed MIT. It adds 128 tokens to every session and 2,680 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…