frappe-role-manager

frappe-role-manager is a command for Claude Code from Venkateshvenki404224/frappe-apps-manager. It costs 14 tokens per session (2,438 once invoked), scanned A, original, MIT.

A command for managing roles and permissions in Frappe, a framework for building business applications. Roles determine what users can access, while permissions control what they can do.

In plain words
What is it for?
Use it to create roles, assign or remove permissions, assign roles to users, view permission settings, and test user access.
Why use it?
It provides a structured way to change access rules and investigate why a user can or cannot access a document type.

Command for Claude Code

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

Part of the frappe-apps-manager plugin — 16 skills, 16 commands, 3 hooks shipped together

Good fit Use it to create roles, assign or remove permissions, assign roles to users, view permission settings, and test user access.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/venkateshvenki404224/frappe-apps-manager/frappe-role-manager
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.

Clone the repo
git clone --depth 1 https://github.com/Venkateshvenki404224/frappe-apps-manager

Made for: Claude Code.

Or install frappe-apps-manager, the plugin that ships this one along with the rest of its 16 skills, 16 commands, 3 hooks.

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 frappe-role-manager

README.md
[![agentmods](https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-role-manager/github.svg)](https://agentmods.dev/commands/venkateshvenki404224/frappe-apps-manager/frappe-role-manager)
Your own site
<a href="https://agentmods.dev/commands/venkateshvenki404224/frappe-apps-manager/frappe-role-manager"><img src="https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-role-manager/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 frappe-role-manager

Your own site · 80×15
<a href="https://agentmods.dev/commands/venkateshvenki404224/frappe-apps-manager/frappe-role-manager"><img src="https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-role-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,438 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.00014 $0.02438
Opus 5 $0.00007 $0.01219
Sonnet 5 $0.00003 $0.00488
Haiku 4.5 $0.00001 $0.00244

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

Security

Grade A, and why

frappe-role-manager 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 12d 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.

frappe-apps-manager/commands/frappe-role-manager.md · 404 lines

How it starts

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

Frappe Role Manager Command

Comprehensive role and permission management for Frappe applications including role creation, permission assignment, and access control.

Steps to Execute

1. Verify Environment

  • Check if in valid Frappe bench
  • Verify site exists
  • Ensure user has System Manager role

2. Operation Selection

Ask user what they want to do:

A. Create New Role

  • Define role name
  • Set role permissions
  • Assign to users

B. Manage Permissions

  • View permission matrix
  • Add/remove permissions
  • Set permission levels

C. Assign Roles to Users

  • Add roles to user
  • Remove roles from user
  • View user roles

D. Test Permissions

  • Test user access to DocType
  • Verify permission rules
  • Debug permission issues

3. Role Creation

Create New Role:

bench --site [site-name] console
# Create role
role = frappe.get_doc({
    'doctype': 'Role',
    'role_name': 'Custom Role',
    'desk_access': 1,  # Can access desk
    'disabled': 0
})
role.insert()
frappe.db.commit()

Role Properties:

  • role_name: Unique role identifier
  • desk_access: 1 = Can access desk, 0 = Portal only
  • two_factor_auth: Require 2FA for this role
  • disabled: 1 = Role disabled

4. Permission Management

Add Permissions to DocType:

# Via console
from frappe.permissions import add_permission

add_permission('Customer', 'Custom Role', perm_level=0)

# Set specific permissions
add_permission('Customer', 'Custom Role',
    read=1, write=1, create=1, delete=0,
    submit=0, cancel=0, amend=0)

frappe.db.commit()

View Permission Matrix:

# Get all permissions for DocType
permissions = frappe.get_all('Custom DocPerm',
    filters={'parent': 'Customer'},
    fields=['role', 'read', 'write', 'create', 'delete', 'submit']
)
print(permissions)

Remove Permissions:

from frappe.permissions import remove_permission

remove_permission('Customer', 'Custom Role')
frappe.db.commit()

5. User Role Assignment

Read the full file on GitHub · 404 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. 12d ago First seen · 404 lines · 14 tokens per session scan A 01eabd84560b

Subscribe to this mod's changes

frappe-role-manager is a command published in the GitHub repository Venkateshvenki404224/frappe-apps-manager (27 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 2,438 once invoked, about $0.0001 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-30.