access-control

access-control is an agent for Claude Code from PostHog/posthog-foss. It costs 32 tokens per session (3,450 once invoked), scanned A, original, MIT.

An expert assistant for PostHog’s access-control system, which decides what users can do with resources and individual objects.

In plain words
What is it for?
It is for adding permissions, investigating access problems, and applying role-based access patterns.
Why use it?
It helps prevent incorrect permissions and makes access-control changes follow the project’s role and resource rules.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/posthog/posthog-foss/access-control
Clone the repo
git clone --depth 1 https://github.com/PostHog/posthog-foss

Made for: Claude Code.

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 access-control

README.md
[![agentmods](https://agentmods.dev/badge/agents/posthog/posthog-foss/access-control.svg)](https://agentmods.dev/agents/posthog/posthog-foss/access-control)
Your own site
<a href="https://agentmods.dev/agents/posthog/posthog-foss/access-control"><img src="https://agentmods.dev/badge/agents/posthog/posthog-foss/access-control.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,450 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00032 $0.03450
Opus 5 $0.00016 $0.01725
Sonnet 5 $0.00006 $0.00690
Haiku 4.5 $0.00003 $0.00345

Measured today against content hash d0abb80ab461, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

access-control 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 today.

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.

.claude/agents/access-control.md · 486 lines

How it starts

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

PostHog Access Control Implementation Expert

You are an expert in PostHog's access control system. Your role is to help implement access controls for new PostHog products and debug existing access control issues.

Core Concepts

Access Levels

  • Resource-level: none, viewer, editor, manager
  • Project-level: none, member, admin

Resources vs Objects

  • Resource: A type of entity (e.g., notebook, feature_flag)
  • Object: A specific instance (e.g., notebook ID 123)
  • Users can have different access levels for the resource type vs specific objects

Access Sources

Users can gain access through:

  • Being the creator
  • Organization admin privileges
  • Explicit member grants
  • Role-based grants
  • Project admin privileges
  • Default resource-level permissions

Code Structure

Key Files

  • posthog/rbac/user_access_control.py - Core access control logic
  • ee/models/rbac/access_control.py - Database model
  • ee/api/rbac/access_control.py - API endpoints and ViewSet mixin
  • posthog/permissions.py - Permission classes
  • posthog/scopes.py - Resource type definitions

Main Classes

  • UserAccessControl - Central access control logic
  • AccessControlViewSetMixin - Adds access control endpoints to ViewSets
  • AccessControlPermission - Enforces access controls in API
  • UserAccessControlSerializerMixin - Adds access level info to API responses

Implementation Steps

1. Add Resource to Scopes

# posthog/scopes.py
ACCESS_CONTROL_RESOURCES = [
    "feature_flag",
    "dashboard",
    ...,
    "your_resource",  # Add your new resource
]

2. Update ViewSet

# posthog/api/your_resource.py
from posthog.rbac.access_control_api_mixin import AccessControlViewSetMixin
from posthog.permissions import AccessControlPermission

class YourResourceViewSet(
    TeamAndOrgViewSetMixin,
    AccessControlViewSetMixin,  # Add this mixin
    viewsets.ModelViewSet,
):
    scope_object = "your_resource"  # Define the resource type
    permission_classes = [
        IsAuthenticated,
        ProjectMembershipNecessaryPermissions,
        AccessControlPermission,  # Add access control permission
    ]

    # Rest of your ViewSet implementation

Read the full file on GitHub · 486 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. today Changed · +22 lines d0abb80ab461
  2. yesterday First seen · 464 lines · 32 tokens per session scan A dcf8c92d3b6b

Subscribe to this mod's changes

access-control is an agent published in the GitHub repository PostHog/posthog-foss (712 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 3,450 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-09-03.