Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. 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/hlalljie/agent-workflow-presets/main/.cursor/skills/issue-labels/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/issue-labels)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/issue-labels"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/issue-labels/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/hlalljie/agent-workflow-presets/issue-labels"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/issue-labels.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.00754 |
| Opus 5.5 | $0.00022 | $0.00302 |
| Sonnet 5.5 | $0.00011 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
issue-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 19d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue labels
The standard
Every issue has one type label. It has a priority label only when the user has set one; no priority label means not prioritized yet.
Type (one per issue; matches the commit types fix, feat, chore or refactor, docs):
bug: Something isn't working.d73a4a(GitHub default).feature: New capability or improvement to existing behavior.a2eeef(GitHub'senhancement, renamed).chore: Maintenance with no user-facing change, such as refactors, dependencies, and CI.c5def5.documentation: Improvements or additions to documentation.0075ca(GitHub default).question: Further information is requested.d876e3(GitHub default).
Priority (at most one per issue; to change it, replace the label):
P0-Critical: Broken or security, drop everything.e11d21.P1-High: Next up.eb6420.P2-Medium: Soon.fbca04.P3-Low: Nice to have.009800.
GitHub's other default labels (duplicate, good first issue, help wanted, invalid, wontfix) stay as they are. Use labels, not GitHub issue types: types exist only on organization repos, and gh issue create --type creates the issue before it can fail.
Setup (once per repo)
Needs Write access or higher. It runs without asking when plan-issues triggers it or the user asks for it. In careful mode, state what will be created and wait for approval.
- Run
gh repo view --json viewerPermission --jq .viewerPermission. If it is notWRITE,MAINTAIN, orADMIN, skip setup, say so in one line, and continue without labels. - Run
gh label list --limit 1000 --json name. Compare names case-insensitively. - If
enhancementexists andfeaturedoes not:gh label edit enhancement --name feature --description "New capability or improvement to existing behavior". - For every other standard label that is missing:
gh label create "<name>" --color <hex> --description "<description>". - Never use
--force, never delete a label, and leave labels outside the standard alone. Once the labels exist, running setup again changes nothing. - Report only what was created or renamed, in one line.
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.
- 19d ago First seen · 44 lines · 56 tokens per session scan A 75538e10dacc
issue-labels is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 56 tokens to every session and 754 once invoked, about $0.0002 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-10-10.
Other skills, from other repositories
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
cast-plan
Turn a request into a plan the team can review before code exists. Explores the codebase, searches prior sessions and recorded decisions for earlier attempts, interviews the user on the open questions, then writes a codecast plan with tasks and dependencies ready for orchestrate. Use when work has several parts, when…
cast-org
Talk through the organization of agents and people around this work with the person, in this session: who reports to whom, what each role looks after, where their sessions go. Reads what the code and the sessions say before it trusts a plan or a task, asks what the records cannot settle, and posts each agreed change…
cast-handoff
Package the current work so the next session or a teammate can continue without reading this thread. Writes the decisions, the direction, what is verified, open questions and ordered next steps as a shared doc, pins the state, and optionally forks, spawns or hands the work to a session. Use before stopping, before a…
cast-loop
Run an autonomous loop that works through a queue of tasks one fresh session at a time, with verification as the gate and a human decision at merge. Sets up a recurring trigger that spawns a session per ready task, a precheck that spends nothing when the queue is empty, and the rules each run follows. Use for a…
cast-conflicts
Before editing or fanning out work, find the live sessions on this repository that are changing the same files, show what they changed, and warn them. Use before starting a task that touches shared files, before spawning workers, or when asked who else is working on this.