Borrowing it
Nothing to install: this file belongs to luanmorenommaciel/agentspec. 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/luanmorenommaciel/agentspec/main/.claude/skills/github-cr-issue/SKILL.mdgit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/luanmorenommaciel/agentspec/github-cr-issue)<a href="https://agentmods.dev/skills/luanmorenommaciel/agentspec/github-cr-issue"><img src="https://agentmods.dev/badge/skills/luanmorenommaciel/agentspec/github-cr-issue/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/luanmorenommaciel/agentspec/github-cr-issue"><img src="https://agentmods.dev/badge/skills/luanmorenommaciel/agentspec/github-cr-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00166 | $0.02379 |
| Opus 5.5 | $0.00066 | $0.00952 |
| Sonnet 5.5 | $0.00033 | $0.00476 |
| Haiku 4.5 | $0.00017 | $0.00238 |
Grade A, and why
github-cr-issue 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 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.
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Issue (GitHub)
Draft the body of one well-formed, non-ADR issue as an ephemeral local file, ready to be reviewed and then published as a GitHub issue by github-post-issue.
A good issue records one topic in a self-contained way. GitHub is the project's state store, agent sessions are stateless workers, and the published issue is the complete spec — any future contributor or agent session must be able to read and act on it with zero private context.
This skill always operates on the repository it is invoked in — the repo is detected dynamically in step 1 and never assumed.
When to use
- The user asks to create, draft, or write an issue — a feature, component, task, bug, or spike.
- A discussion, idea, or defect report needs to become a tracked, actionable GitHub issue.
- A large initiative needs structuring as a parent issue with sub-issues.
Skip if
| Situation | Do instead | Why |
|---|---|---|
| Architecture decision (which option and why) | github-cr-adr |
Features and components link to decisions; they do not contain them. |
| A finished draft needs publishing, labels, or relationships | github-post-issue |
Publication has its own guardrails: dedup, self-containment, label validation. |
| Updating an issue that already exists | gh issue comment / gh issue edit |
The existing issue is the record; extend it instead of forking it. |
| Trivial, immediate change | Fix it directly | An issue that outlives the work it describes is pure overhead. |
Issue types
Pick exactly one type per issue.
| Type | Use for | Title format |
|---|---|---|
feature |
A capability to add, for users or developers | [FEATURE] … |
component |
A reusable building block or subsystem with a defined contract | [COMPONENT] … |
task |
A concrete unit of work, usually a child of a feature, component, or ADR | [TASK] … |
bug |
A defect, with reproduction steps and expected vs actual behavior | [BUG] … |
spike |
A time-boxed investigation: one question, one deliverable | [SPIKE] … |
What ships with it
1 file 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.
- 1mo ago First seen · 158 lines · 166 tokens per session scan A 27aa590fe32c
github-cr-issue is a skill published in the GitHub repository luanmorenommaciel/agentspec (256 stars, last pushed 3d ago), licensed MIT. It adds 166 tokens to every session and 2,379 once invoked, about $0.0007 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-09-01.
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.
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…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
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…