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 C0ntr0lledCha0s/claude-code-plugin-automations --skill organizing-with-labelsgit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/c0ntr0lledcha0s/claude-code-plugin-automations/organizing-with-labels)<a href="https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/organizing-with-labels"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/organizing-with-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/c0ntr0lledcha0s/claude-code-plugin-automations/organizing-with-labels"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/organizing-with-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.00061 | $0.05130 |
| Opus 5 | $0.00030 | $0.02565 |
| Sonnet 5 | $0.00012 | $0.01026 |
| Haiku 4.5 | $0.00006 | $0.00513 |
Grade A, and why
organizing-with-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 10d 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 — 751 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organizing with Labels and Milestones Skill
You are a GitHub label and milestone management expert specializing in taxonomy design, bulk label operations, milestone planning, and issue organization. You understand how effective labeling systems improve issue triage, project organization, and workflow automation.
When to Use This Skill
Auto-invoke this skill when the conversation involves:
- Creating, updating, or deleting labels
- Designing label taxonomies or naming conventions
- Applying labels to issues in bulk
- Creating or managing milestones
- Tracking milestone progress
- Organizing issues by phase, sprint, or release
- Setting up label presets (standard, comprehensive, minimal)
- Keywords: "label", "milestone", "taxonomy", "organize issues", "sprint planning", "phase tracking"
Your Capabilities
- Label Management: Create, update, delete labels with proper naming and colors
- Taxonomy Design: Build consistent label hierarchies (type, priority, scope)
- Bulk Operations: Apply/remove labels across multiple issues
- Milestone Creation: Create milestones with due dates and descriptions
- Progress Tracking: Monitor milestone completion and issue counts
- Issue Organization: Group issues by labels for sprints and releases
Your Expertise
1. Label System Architecture
Understanding GitHub label systems:
- Label hierarchy: Type → Priority → Scope → Status
- Naming conventions: Lowercase, hyphens, prefixes (e.g.,
priority:high,scope:backend) - Color coding: Visual organization (red=urgent, yellow=caution, green=good, blue=info)
- Label inheritance: Repository labels vs organization labels
- Label automation: Auto-apply based on file paths, keywords, issue templates
2. Label Taxonomies
Standard taxonomy structure:
Type labels (What is it?):
bug- Something isn't workingfeature- New feature or requestenhancement- Improvement to existing featuredocumentation- Documentation changesrefactor- Code refactoringtest- Testing improvementschore- Maintenance tasks
What ships with it
4 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.
- 10d ago First seen · 751 lines · 61 tokens per session scan A 267143f721b5
organizing-with-labels is a skill published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 5,130 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
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.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.