speckit.identity-access

speckit.identity-access is a skill for Claude Code, Codex from wedabro/bro-skills. It costs 30 tokens per session (883 once invoked), scanned A, original, MIT.

An identity and access engineering guide for designing authentication, permissions, login federation, user provisioning, sessions, and account lifecycles. Authentication confirms who someone is; authorization controls what they may do.

In plain words
What is it for?
Designing OAuth/OIDC login, roles and permissions, tokens and sessions, recovery, account changes, deletion, and related audit events.
Why use it?
It helps make access flows secure, standards-based, auditable, and usable when accounts or identity services fail.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Designing OAuth/OIDC login, roles and permissions, tokens and sessions, recovery, account changes, deletion, and related audit events.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wedabro/bro-skills/speckit.identity-access
Install

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.

Any agent
npx skills add wedabro/bro-skills --skill speckit.identity-access
Clone the repo
git clone --depth 1 https://github.com/wedabro/bro-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for speckit.identity-access

README.md
[![agentmods](https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.identity-access/github.svg)](https://agentmods.dev/skills/wedabro/bro-skills/speckit.identity-access)
Your own site
<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.identity-access"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.identity-access/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.

agentmods 80×15 button for speckit.identity-access

Your own site · 80×15
<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.identity-access"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.identity-access.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 883 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00883
Opus 5 $0.00015 $0.00441
Sonnet 5 $0.00006 $0.00177
Haiku 4.5 $0.00003 $0.00088

Measured 11d ago against content hash 6190238abdba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

speckit.identity-access 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 11d 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.

.agents/skills/speckit.identity-access/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mission

Design identity and access flows that are standards-based, usable, auditable, and safe under failure. Use this skill for authentication and authorization architecture; use speckit.security to audit the completed implementation and speckit.backend to implement service boundaries.

Required Inputs

  • Actors, roles/permissions, tenancy, data sensitivity, regulatory constraints, supported clients, recovery needs, and existing identity provider contracts.
  • The feature spec, threat model, session/token storage constraints, and user lifecycle requirements (join, change role, disable, recover, delete).

Protocol

0. Identity Decision Record

  • State authenticators, relying parties, identity provider, trust boundaries, token/session model, credential storage, recovery channel, audit events, and availability/failure behavior before implementation.
  • Choose the simplest standards-based flow compatible with the clients. For browser/native delegated login, prefer OAuth 2.0/OIDC authorization code with PKCE; do not use implicit flow or expose client secrets in public clients.

1. Authentication and Sessions

  • Verify issuer, audience, signature, expiry, nonce/state, redirect URI, and required claims before accepting an identity assertion. Use short-lived, scoped credentials and rotation/revocation appropriate to the risk.
  • Use secure, HttpOnly, SameSite cookies for browser sessions when practical; protect state-changing cookie requests from CSRF. Never put secrets or long-lived credentials in URLs, logs, browser storage, or client bundles.
  • Implement rate limits, credential-stuffing defenses, secure password hashing where passwords exist, MFA/passkey enrollment, recovery, logout, session invalidation, and concurrent-session policy deliberately.

2. Authorization and Tenancy

  • Model permissions around actions and resources, not UI visibility. Enforce RBAC, ABAC, or policy checks server-side on every sensitive read and write.
  • Check object ownership, organization/tenant membership, role state, and scope at the use-case boundary. Never trust a client role, owner ID, or tenant ID.
  • Propagate actor, tenant, delegated authority, and correlation context through APIs, jobs, caches, and data access. For tenant systems, add database-level isolation where feasible and test cross-tenant denial explicitly.
  • Define privileged/admin break-glass access, approval, audit, expiry, and review. Apply least privilege by default and deny on missing context.

Read the full file on GitHub · 86 lines

Changes

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.

  1. 11d ago First seen · 86 lines · 30 tokens per session scan A 6190238abdba

Subscribe to this mod's changes

speckit.identity-access is a skill published in the GitHub repository wedabro/bro-skills (2 stars, last pushed 15d ago), licensed MIT. It adds 30 tokens to every session and 883 once invoked, about $0.0002 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.