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/github-conventions/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/github-conventions)<a href="https://agentmods.dev/skills/qauth-labs/qauth/github-conventions"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/github-conventions/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/github-conventions"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/github-conventions.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.00086 | $0.00811 |
| Opus 5.5 | $0.00034 | $0.00324 |
| Sonnet 5.5 | $0.00017 | $0.00162 |
| Haiku 4.5 | $0.00009 | $0.00081 |
Grade A, and why
github-conventions 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Conventions (QAuth)
Shared conventions for GitHub work on QAuth. The focused operation skills load only their own commands and reference this skill for the conventions below, so no single task pulls in unrelated context.
Tooling
QAuth uses the gh CLI for GitHub operations — deliberately preferred over
the GitHub MCP server as of this refactor. (Revisit this choice on the next
agentic-docs refactor.) All examples in the GitHub skills use gh.
- Repo:
qauth-labs/qauth - Project scope: some project commands need
gh auth refresh -s projectonce.
Branch Naming
<type>/<issue>-slug, e.g. feature/62-oauth-token-endpoint,
fix/67-rewrite-dbseed, docs/…, refactor/…, chore/….
Conventional Commits & Titles
Commit messages and PR/issue titles follow Conventional Commits:
feat:, fix:, refactor:, docs:, style:, perf:, test:, chore:.
Add a scope where useful: feat(auth): …. Common scopes: auth, oauth, db,
config, ci, api, docker.
Issue Body Template
## Summary
{1-2 sentence description}
## Tasks
- [ ] Task 1
- [ ] Task 2
## Technical Details
{code examples, config, architecture notes}
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## References
- docs/adr/{ADR file} - {relevant section}
PR Body Template
Lead with the issue link so it auto-closes on merge, then concise bullets:
Closes #62
- Bullet point of change 1
- Bullet point of change 2
Use Fixes #N for bug fixes, Closes #N for features.
Labels & Milestones
- Labels:
enhancement(features),bug(fixes); add others as needed (e.g.priority:high,auth). - Milestone: new work goes on a release milestone of the 0.x → 1.0 path
(ADR-018 §2), whose titles carry a descriptive suffix — e.g.
v0.3 - Core and UIs beta. The olderMVPandT0–T6milestones are finished history; never file new work against them. There has never been aPhase Nmilestone. Read the live list before setting one, because this file cannot stay ahead of it:
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 · -2 lines 5ef0b0b9cc04
- 1mo ago Changed · +9 lines 8025968d70dc
- 1mo ago First seen · 89 lines · 86 tokens per session scan A 5abd18065e3d
github-conventions is a skill published in the GitHub repository qauth-labs/qauth (26 stars, last pushed today), licensed Apache-2.0. It adds 86 tokens to every session and 811 once invoked, about $0.0003 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
source-code-management
Create or review caddy-security commit messages using repository indicators, required body sections, and timestamped message files. A message request does not create a commit.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.