Borrowing it
Nothing to install: this file belongs to jd-solanki/airig. 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/jd-solanki/airig/main/.ai/skills/krutrimbox-github-labels/SKILL.mdgit clone --depth 1 https://github.com/jd-solanki/airigWrote 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/jd-solanki/airig/krutrimbox-github-labels)<a href="https://agentmods.dev/skills/jd-solanki/airig/krutrimbox-github-labels"><img src="https://agentmods.dev/badge/skills/jd-solanki/airig/krutrimbox-github-labels.svg" alt="Measured on agentmods" 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.00052 | $0.00947 |
| Opus 5 | $0.00026 | $0.00474 |
| Sonnet 5 | $0.00010 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
github-labels 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Labels
Use this skill to choose issue and PR labels before publishing or updating GitHub tracker items. Apply the smallest accurate label set, and if a required label does not exist in the repository, create it with GitHub CLI before applying it.
krutrimbox discovers a Target Issue as an open issue labeled ready-for-agent that has no parent issue. A Target Issue is either Standalone (no sub-issues; its own body is the work) or a Parent (its native GitHub sub-issues are the Implementation Issues). Membership in a Parent Target Issue is the native sub-issue link, not a label. The retired PRD and PRD-sub-issue labels are no longer used.
Quick Start
- Standalone Target Issue, fully specified: apply
ready-for-agent - Parent Target Issue: apply
ready-for-agentonly after every Implementation Issue has been created and linked - Implementation Issue (sub-issue): apply exactly one of
ready-for-agentorready-for-human(no membership label — the native sub-issue link is the membership) - Unevaluated issue: apply
needs-triage, orneeds-infowhen a specific answer is required - Pull request opened by krutrimbox:
krutrimbox
Labels
| Label | Meaning |
|---|---|
ready-for-agent |
Fully specified and ready for an AFK agent — the discovery signal on a Target Issue, and the AFK-readiness marker on an Implementation Issue |
ready-for-human |
An Implementation Issue that requires human work before krutrimbox can continue (HITL) |
needs-triage |
Maintainer needs to evaluate this issue |
needs-info |
Waiting on the reporter for more information |
wontfix |
Will not be actioned |
krutrimbox |
Pull request created and maintained by krutrimbox |
Labeling Workflow
- Identify the artifact: Standalone Target Issue, Parent Target Issue, Implementation Issue (sub-issue), or pull request.
- Decide whether the work is specified enough to start.
- For a Standalone Target Issue (self-contained, no sub-issues): apply
ready-for-agentwhen it is fully specified with clear acceptance criteria; otherwiseneeds-triageorneeds-info. No parent and no PRD ceremony are required. - For a Parent Target Issue: keep it at
needs-triageuntil every approved Implementation Issue has been created and linked as a native sub-issue, then applyready-for-agentso krutrimbox discovers it and walks its sub-issues. - For an Implementation Issue (native sub-issue): apply exactly one state label —
ready-for-agent(AFK) orready-for-human(HITL). Do not add a membership label; the native sub-issue link is the membership. - For a pull request: krutrimbox labels its own PR
krutrimbox. Mirror an issue's readiness on a PR only if the repository conventionally does so.
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 · 57 lines · 52 tokens per session scan A 7e5db2d9cbff
github-labels is a skill published in the GitHub repository jd-solanki/airig (2 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 947 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.