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/create-prnpx skills add qauth-labs/qauth --skill create-prgit 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-pr)<a href="https://agentmods.dev/skills/qauth-labs/qauth/create-pr"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/create-pr.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00367 |
| Opus 5 | $0.00008 | $0.00183 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
create-pr 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 4d 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.
What it actually says
Create Pull Request
Create a PR with gh pr create. For the title format (Conventional Commits +
scope) and PR body format (Closes #N / Fixes #N + bullets), follow the
github-conventions skill.
Pre-PR Checklist
git status # no unintended uncommitted changes
pnpm nx affected -t lint # lint passes
pnpm nx affected -t test # tests pass
pnpm nx affected -t typecheck # types pass
Command
gh pr create \
--title "feat(scope): description" \
--body "$(cat <<'EOF'
Closes #XX
- Change 1
- Change 2
EOF
)"
Example (feature)
Closes #62
- Add TOKEN_RATE_LIMIT and TOKEN_RATE_WINDOW to auth config (30/min, 60s)
- Add MIN_RESPONSE_TIME_MS.TOKEN (300ms) for timing-attack mitigation
- Implement POST /oauth/token: client_secret_post, PKCE, code validation
- Rate limit by IP; audit oauth.token.exchange.success/failure
Instructions
- Review the changes with
git diffandgit log. - Identify which issue(s) this PR closes.
- Write concise bullet points describing each change; pick the right
Conventional Commit title (see
github-conventions). - Include
Closes #X/Fixes #Xto auto-link issues. - Create the PR and report the URL 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.
- 4d ago First seen · 55 lines · 15 tokens per session scan A 8b61cc0029c1
create-pr is a skill published in the GitHub repository qauth-labs/qauth (24 stars, last pushed 8d ago), licensed Apache-2.0. It adds 15 tokens to every session and 367 once invoked, about $0.0001 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-portal-ui
Guidelines for updating or designing pages in the portal React frontend (portal/src). Covers component conventions, link rendering rules, i18n patterns, and common pitfalls.