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/authgear/authgear-server/bootstrap-local-devnpx skills add authgear/authgear-server --skill bootstrap-local-devgit clone --depth 1 https://github.com/authgear/authgear-serverWhat 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.00071 | $0.01547 |
| Opus 5 | $0.00036 | $0.00773 |
| Sonnet 5 | $0.00014 | $0.00309 |
| Haiku 4.5 | $0.00007 | $0.00155 |
Grade A, and why
bootstrap-local-dev 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Walk a contributor through first-time setup of this repo. Run steps in order, verify each one before moving on, and stop on the first failure so the user can fix it.
This skill assumes macOS + zsh/bash. Linux works for most steps but the Homebrew commands need adapting; if uname is not Darwin, warn the user up front and offer to fall back to CONTRIBUTING.md.
If the user already has a working local dev environment, do not run this skill — use the "Start local dev" recipe in AGENTS.md instead.
Step 0: Preflight
-
Confirm the working directory is the repo root:
git rev-parse --show-toplevelshould print the path toauthgear-server. -
Read
.tool-versionsto know which versions are pinned. The current pin is:golang 1.26.2 nodejs 20.19.5 python 3.12.1If the file has different versions, use the file's values everywhere below.
-
Verify
asdf --version≥0.14. If asdf is not installed, prompt the user to install it (https://asdf-vm.com/guide/getting-started.html) and pause — do not continue.
Verify: git rev-parse --show-toplevel succeeds, .tool-versions is readable, asdf --version prints a version.
Step 1: Install pinned tool versions via asdf
Run:
asdf plugin add golang https://github.com/asdf-community/asdf-golang.git
asdf plugin add nodejs https://github.com/asdf-vm/asdf-nodejs.git
asdf plugin add python
asdf install
Plugin-add commands are idempotent and will report "already added" if the plugin exists; that's fine, continue.
Verify: in the repo root, asdf current shows golang, nodejs, python all sourced from this repo's .tool-versions and marked installed. which go should point under ~/.asdf/, and go version should match the pinned Go version.
Step 2: Install Homebrew system dependencies
These need Homebrew prompts / sudo, so do NOT run them yourself. Prompt the user to run:
brew install make coreutils pkg-config icu4c vips libmagic
After they confirm completion, set up the required environment exports. Compute the right paths:
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 · 138 lines · 71 tokens per session scan A 15999824fe6d
bootstrap-local-dev is a skill published in the GitHub repository authgear/authgear-server (2,017 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 1,547 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
auth0-docs
Auth0 — identity platform: auth flows, Universal Login, SSO, identity providers, MFA, RBAC, Actions, tokens.
zeroid
MANUAL TRIGGER ONLY: invoke only when user types /zeroid. Identity infrastructure for AI agents — register identities, issue tokens, delegate to sub-agents, revoke credentials, and manage credential policies via the Zeroid REST API.
zeroid
Identity infrastructure for AI agents — register identities, issue tokens, delegate to sub-agents, revoke credentials, manage policies.
auth-oauth
Implements and reviews OAuth 2.0/2.1 flows following RFC 6749, RFC 9700 (BCP), and PKCE (RFC 7636). Use when implementing authorization code flow, token handling, client registration, or securing OAuth endpoints.
schema
Database schema rules for QAuth. Use when working with the identity model, Drizzle ORM, migrations, repositories, or claim resolution. Reflects the CURRENT shipped schema — the identifier-abstraction model (ADR-002, IMPLEMENTED via Epic.
fastify
Fastify usage for QAuth — plugin authoring (encapsulation, decorators, lifecycle), route schemas with the Zod type provider, production/reverse-proxy setup, and the Fastify version/CVE requirement. Use when adding or modifying @qauth-labs/fastify-plugin- libraries, auth-server routes, or deployment config.