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 agentmods add skills/qauth-labs/qauth/github-conventionsnpx skills add qauth-labs/qauth --skill github-conventionsgit clone --depth 1 https://github.com/qauth-labs/qauthWhat 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 | $0.00086 | $0.00699 |
| Opus 5 | $0.00043 | $0.00349 |
| Sonnet 5 | $0.00017 | $0.00140 |
| Haiku 4.5 | $0.00009 | $0.00070 |
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 2d 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 — 89 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
- MVP-PRD.md - {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: MVP issues use
MVP. Phases: Phase 0 Foundation, Phase 1 Core Auth, Phase 2 Developer Portal, Phase 3 Production Readiness.
Focused Skills
create-issue— create an issuecreate-pr— open a pull requestadd-sub-issue— parent/child issue links (GraphQL)add-to-project— add an issue to a project boardinvestigate-issue— gather context/requirements for an issueset-milestone— manage milestones on issues
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.
- 2d 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 (24 stars, last pushed 7d ago), licensed Apache-2.0. It adds 86 tokens to every session and 699 once invoked, about $0.0004 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-30.
Other skills, from other repositories
write-e2e-test
Write end-to-end (e2e) tests for authgear-server. Use when the user asks to write, add, or create e2e tests. The tests live in e2e/tests/ and are YAML-driven.
add-portal-screen
Add screens or components to the portal frontend. Use when the user asks to create a new portal page, screen, tab, or UI component.
api-design
Review or design APIs for Authgear. In review mode, evaluates a design draft against the checklist. In ideation mode, develops a design from a description and self-reviews it.
update-deps
Audit and fix dependency vulnerabilities in Go and Node.js packages. Runs govulncheck for Go and npm audit for each package.json directory. Commits fixes directory by directory.
new-siteadmin-api
Full pipeline for adding a new Site Admin API feature — from OpenAPI spec through implementation plan to working service. Use when adding a new endpoint or filling in real data for an existing stub.
update-feature-config
Add or change a feature config field/section in pkg/lib/config (authgear.features.yaml). Use when adding a new feature config field, adding a new top-level section, or touching an existing section's Merge implementation.