Borrowing it
Nothing to install: this file belongs to qauth-labs/qauth. 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/qauth-labs/qauth/main/.claude/skills/create-issue/SKILL.mdgit clone --depth 1 https://github.com/qauth-labs/qauthWrote 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/qauth-labs/qauth/create-issue)<a href="https://agentmods.dev/skills/qauth-labs/qauth/create-issue"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/create-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/qauth-labs/qauth/create-issue"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/create-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.00019 | $0.00404 |
| Opus 5.5 | $0.00008 | $0.00162 |
| Sonnet 5.5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
create-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 yesterday.
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.
What it actually says
Create GitHub Issue
Create a GitHub issue with gh issue create. For title format, the issue body
template, labels, and milestones, follow the github-conventions skill.
Command Template
gh issue create \
--title "feat: {title}" \
--body "$(cat <<'BODY'
## Summary
{summary}
## Tasks
- [ ] {task1}
- [ ] {task2}
## Technical Details
{details}
## Acceptance Criteria
- [ ] {criterion1}
- [ ] {criterion2}
## References
- docs/adr/018-1-0-scope-and-stability.md - {relevant section}
BODY
)" \
--label "enhancement" \
--milestone "$MILESTONE"
Set MILESTONE from the live list, never from memory. New work goes on a release
milestone (v0.2 … v1.0); filing it against a finished one (MVP, T0–T6)
buries the issue:
gh api repos/qauth-labs/qauth/milestones --jq '.[] | select(.state=="open") | .title'
Omit --milestone entirely if no open milestone fits; an unmilestoned issue is better
than a misfiled one.
Instructions
- Ask the user what they want to create if it isn't clear.
- Determine the appropriate phase (see
github-conventionsfor phases). - Write detailed tasks with checkboxes and clear acceptance criteria; include technical details/code examples where relevant.
- Create the issue with
gh issue create. - Report the issue URL back to the user.
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.
- yesterday Changed · +1 lines df9e6c669cbd
- 1mo ago Changed · +10 lines b3d4625f074f
- 1mo ago First seen · 53 lines · 19 tokens per session scan A 1e6639765d04
create-issue is a skill published in the GitHub repository qauth-labs/qauth (26 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 404 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
Clerk Auth Testing
Testing patterns for Clerk authentication including sign-in flow testing, protected route testing, webhook verification, middleware testing, and organization-based access control.
firebase-auth-better-auth
Add Firebase Authentication (Phone SMS OTP, Google Sign-In, Email/Password) to a Better Auth app using the better-auth-firebase-auth plugin. Use when adding phone authentication to Better Auth without Twilio, integrating Firebase Auth with Better Auth sessions, working with the better-auth-firebase-auth package, or…
theauth
Install and use theAuth (@glinr/theauth), the TypeScript auth SDK for AI agents and humans. Use when adding agent identity, scoped permissions, delegation, audit logs, human sign-in plugins, or an MCP OAuth 2.1 authorization server to a Node, Bun, Deno or edge project.
crudauth
Use when building or modifying authentication in a FastAPI app with crudauth (the crudauth PyPI package) — covers CRUDAuth, the AuthUserMixin / makeauthidentity user model, IdentityConfig, currentuser(...) gates, session + bearer transports, OAuth (Google/GitHub), email verification / password reset / change, custom…
forge-feature
Own the full feature lifecycle (frame, plan, implement, check, done, resume, accept-risk, abandon) with CLI-enforced statuses. Use for building, continuing, or shipping a specific feature in build mode.
nextjs-authentication
Secure token storage (HttpOnly Cookies) and Middleware patterns. Use when implementing authentication, secure session storage, or auth middleware in Next.js.