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 agents/posthog/posthog-foss/access-controlgit clone --depth 1 https://github.com/PostHog/posthog-fossWrote 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.
[](https://agentmods.dev/agents/posthog/posthog-foss/access-control)<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>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.
| Model | Per session | Once 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 |
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.
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 logicee/models/rbac/access_control.py- Database modelee/api/rbac/access_control.py- API endpoints and ViewSet mixinposthog/permissions.py- Permission classesposthog/scopes.py- Resource type definitions
Main Classes
UserAccessControl- Central access control logicAccessControlViewSetMixin- Adds access control endpoints to ViewSetsAccessControlPermission- Enforces access controls in APIUserAccessControlSerializerMixin- 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
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.
- today Changed · +22 lines d0abb80ab461
- yesterday First seen · 464 lines · 32 tokens per session scan A dcf8c92d3b6b
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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.