permissions-and-settings

permissions-and-settings is a skill for Claude Code from oborchers/fractional-cto. It costs 63 tokens per session (788 once invoked), scanned A, original, MIT.

A set of guidance for controlling which users can see and change parts of an application. It covers role-based access control, meaning permissions assigned to roles such as admin or member, along with invitations, settings, and feature restrictions.

In plain words
What is it for?
Use it to design role permissions, admin panels, invitation flows, account and workspace settings, and features limited by user role or plan.
Why use it?
It helps prevent users from seeing irrelevant controls or attempting actions they cannot perform. It also helps explain restricted features without making the interface confusing.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the saas-design-principles plugin — 13 skills, 1 command, 1 agent shipped together

Good fit Use it to design role permissions, admin panels, invitation flows, account and workspace settings, and features limited by user role or plan.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oborchers/fractional-cto/permissions-and-settings
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 oborchers/fractional-cto --skill permissions-and-settings
Clone the repo
git clone --depth 1 https://github.com/oborchers/fractional-cto

Made for: Claude Code.

Or install saas-design-principles, the plugin that ships this one along with the rest of its 13 skills, 1 command, 1 agent.

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 permissions-and-settings

README.md
[![agentmods](https://agentmods.dev/badge/skills/oborchers/fractional-cto/permissions-and-settings/github.svg)](https://agentmods.dev/skills/oborchers/fractional-cto/permissions-and-settings)
Your own site
<a href="https://agentmods.dev/skills/oborchers/fractional-cto/permissions-and-settings"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/permissions-and-settings/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 permissions-and-settings

Your own site · 80×15
<a href="https://agentmods.dev/skills/oborchers/fractional-cto/permissions-and-settings"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/permissions-and-settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 788 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.00063 $0.00788
Opus 5.5 $0.00025 $0.00315
Sonnet 5.5 $0.00013 $0.00158
Haiku 4.5 $0.00006 $0.00079

Measured 5d ago against content hash 112bf77d6a6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

permissions-and-settings 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 5d 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.

saas-design-principles/skills/permissions-and-settings/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.

Permissions Should Be Felt, Not Fought

Every user should see exactly what they need to get their job done — no more, no less.

Three Strategies for Restricted Features

All three are needed — choose per feature:

Strategy When to Use Example
Hide completely Entire section irrelevant to the role Admin-only billing section hidden from members
Show but disable (with tooltip) User should know the feature exists — upsell path Plan-gated feature with "Upgrade to Pro" tooltip
Show with reduced functionality Read access appropriate, write access isn't View-only dashboard for member role

RBAC Progression

Follow WorkOS's practical progression, building incrementally:

  1. Simple admin/member differentiation — start here
  2. Fine-grained permissions per feature — define what each role can do
  3. Roll-up roles — combine permissions into named roles
  4. Resource groups — scope roles to orgs, teams, projects
  5. Custom roles — let admins define their own
  6. IdP attribute mapping — for enterprise SSO

Key UX guardrail: Expose permission bundles that map to real product concepts, not 40 atomic checkboxes. Enforce limits like "max 20 custom roles per tenant" to prevent configuration chaos.

Invitation Flows

Three mechanisms are needed:

1. Email Invite (Default)

Admin enters addresses, sets access level before sending.

2. Link Invite (Bulk)

For bulk invitations. Support expiration dates and domain restrictions.

3. Domain-Based Provisioning (Enterprise SSO)

Accounts auto-created on first login.

Invitation email must include:

  • Who invited them
  • What the product does
  • Who else from their team is already using it

Differentiate onboarding for invited users — they get a shorter, different flow because context already exists.

Settings Architecture

Clean split between two concerns:

Settings Type Belongs To Examples
Account settings The person Profile, password, notifications, appearance
Workspace settings The organization Members, billing, integrations, security policies

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. 5d ago First seen · 86 lines · 63 tokens per session scan A 112bf77d6a6c

Subscribe to this mod's changes

permissions-and-settings is a skill published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. It adds 63 tokens to every session and 788 once invoked, about $0.0003 per session on Opus 5.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-10-13.

Related

Other skills, from other repositories

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 52 tokens

glance-canonical-layouts

Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).

android/skills · 56 tokens

accessibility

Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.

microsoft/hve-core · 47 tokens