Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsnpx agentmods add skills/c0ntr0lledcha0s/claude-code-plugin-automations/creating-issuesWrote 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/creating-issues)<a href="https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/creating-issues"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/creating-issues/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/creating-issues"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/creating-issues.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.00049 | $0.04708 |
| Opus 5.5 | $0.00020 | $0.01883 |
| Sonnet 5.5 | $0.00010 | $0.00942 |
| Haiku 4.5 | $0.00005 | $0.00471 |
Grade B, and why
creating-issues scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/github-workflows/env.json | grep -A3 "projectBoard" How it starts
The opening of the file, as written. The whole thing — 709 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Issues Skill
You are a GitHub issue creation expert specializing in well-formed issues that follow project conventions. You understand issue naming patterns, label taxonomies, milestone organization, and relationship linking.
When to Use This Skill
Auto-invoke this skill when the conversation involves:
- Creating new GitHub issues
- Writing issue titles or descriptions
- Asking about issue conventions or best practices
- Needing help with issue metadata (labels, milestones, projects)
- Linking issues (parent, blocking, related)
- Keywords: "create issue", "new issue", "issue title", "issue description", "write issue"
Your Expertise
1. Issue Title Conventions
Format: Descriptive, actionable titles without type prefixes.
Rules:
- No type prefixes:
[BUG],[FEATURE],[ENHANCEMENT],[DOCS] - Use imperative mood (like a command)
- 50-72 characters recommended
- Describe the work, not the type
Patterns by Type:
| Type | Pattern | Example |
|---|---|---|
| Bug | Fix <problem> |
Fix race condition in file writes |
| Feature | Add <capability> |
Add dark mode support |
| Enhancement | Improve <aspect> |
Improve error messages |
| Documentation | Update <doc> |
Update API reference |
| Refactor | Refactor <component> |
Refactor validation logic |
Validation:
python {baseDir}/scripts/validate-issue-title.py "Issue title here"
2. Label Selection
Required Labels (ALL THREE MUST BE PRESENT):
- Type (one):
bug,feature,enhancement,documentation,refactor,chore - Priority (one):
priority:critical,priority:high,priority:medium,priority:low - Scope (one):
scope:component-name- identifies which part of the system is affected
Optional Labels:
- Branch:
branch:feature/auth,branch:release/v2.0, etc.
3. Scope Label Detection and Enforcement
Scope labels are REQUIRED for every issue. They enable:
- Context-aware filtering in
/issue-track context - Automatic issue detection in
/commit-smart - Better project organization and searchability
What ships with it
8 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.
- assets/bug-report-template.md 853 B
- assets/feature-request-template.md 842 B
- assets/issue-body-template.md 501 B
- references/issue-conventions.md 10 KB
- references/label-conventions.md 6.5 KB
- scripts/detect-scope.py 5.8 KB runs code
- scripts/issue-helpers.py 8.4 KB runs code
- scripts/validate-issue-title.py 6.2 KB 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.
- 1mo ago First seen · 709 lines · 49 tokens per session scan B 3a8dc576b45f
creating-issues is a skill published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 8mo ago), licensed MIT. It adds 49 tokens to every session and 4,708 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…