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/kouroshez/coding-os/auth-patternsnpx skills add kouroshez/coding-os --skill auth-patternsgit clone --depth 1 https://github.com/kouroshez/coding-osWhat 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.00118 | $0.04095 |
| Opus 5 | $0.00059 | $0.02048 |
| Sonnet 5 | $0.00024 | $0.00819 |
| Haiku 4.5 | $0.00012 | $0.00409 |
Grade A, and why
auth-patterns 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth Patterns — Sessions, Tokens, Identity
Practical authentication + authorization patterns for the project's stack: React Native client → Go+Fiber business backend → Python+FastAPI AI adapter → PostgreSQL. Designed around 2026-current best practices and the realistic threat model of a consumer mobile app.
When to Use This Skill
- Adding sign-in to a new service.
- Choosing JWT vs opaque sessions for the RN ↔ Go ↔ FastAPI token chain.
- Designing refresh-token rotation + revocation.
- Integrating a hosted identity provider (Better-Auth, Clerk, Auth0, WorkOS).
- Implementing magic-link / OTP / passkey flows.
- Adding 2FA (TOTP + backup codes).
- Defining the permissions model — RBAC vs ABAC vs ReBAC.
- Designing the password reset flow (it's the most-broken thing in most apps).
- Hardening an existing auth surface — cookie flags, CSRF, header rules.
Default Stack — One Sentence
Server-side opaque sessions stored in Postgres + a short-lived signed access JWT for service-to-service hops. The RN app holds the opaque session token in Keychain/Keystore. The Go backend exchanges that for a 5-minute service JWT when it needs to call the FastAPI AI adapter. No long-lived JWTs anywhere on the client.
This combines the revocability of sessions, the statelessness of JWTs where it matters (between services), and the robust mobile storage of native secure stores.
For the alternatives and when each is right, see references/sessions-vs-jwt.md.
Core Decision: Session vs JWT
| Factor | Server sessions (opaque token) | JWT (signed claims) |
|---|---|---|
| Revocation | Instant — delete row | Hard — needs blocklist or short TTL |
| Read cost per request | DB lookup (or Redis) | Verify signature (cheap) |
| Cross-service auth | Need to share session store or call back | Self-contained, just verify |
| Mobile-friendly | Trivial (any opaque token) | Same |
| Browser-friendly | Cookies + CSRF protection | Cookies, header, or localStorage (each with risks) |
| Auditable | Easy — table of active sessions per user | Hard unless you track usage |
| Logout-from-all-devices | DELETE WHERE user_id = X | Only with a per-user revocation versioning trick |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 353 lines · 118 tokens per session scan A ca5b1c7002ed
auth-patterns is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 118 tokens to every session and 4,095 once invoked, about $0.0006 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-31.
Other skills, from other repositories
potpie-source-ingestion
Use when the user explicitly asks to ingest, refresh, or deeply understand a repository, PR, issue, ticket, runbook, incident report, document, or web link into Potpie. The harness performs todo-driven discovery, uses local/GitHub/integration tools and read-only subagents when available, builds evidence-backed…
potpie-repo-baseline
Use when establishing, refreshing, or deeply understanding a repository's baseline memory in Potpie: purpose, application type, features, services/modules, environments, deploy shape, dependencies, API contracts, datastores, integrations, ownership, and explicit preferences. The harness reads authored and…
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…
alfworld-locate-target-object
Navigates to a suspected location and identifies a target object. Use when your goal requires finding a specific object (e.g., "potato", "plate") and its location is not immediately known. Moves to a relevant receptacle (like a fridge or cabinet), checks its contents, and outputs the object's location or confirms its…
scienceworld-growth-focuser
Use when you have planted a seed or need to track a plant's growth stage (sprouting, flowering, reproduction). Applies the 'focus on' action to a specific plant or biological entity to signal intent and monitor its development. Trigger after planting or when you need to observe life cycle progression in the…