perms

A command guide for LuckPerms, a Minecraft server tool that controls player groups and permissions.

In plain words
What is it for?
Use it to create rank ladders, assign permission nodes, configure group prefixes and weights, and give ordered `/lp` commands.
Why use it?
It helps set up permission hierarchies and avoids guessing plugin permission names or applying access in the wrong server or world.

Command

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 commands/teddy563/mcwrench/perms
Clone the repo
git clone --depth 1 https://github.com/Teddy563/mcwrench
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 135 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.00017 $0.00135
Opus 5 $0.00009 $0.00068
Sonnet 5 $0.00003 $0.00027
Haiku 4.5 $0.00002 $0.00014

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

Security

Grade A, and why

perms 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 yesterday.

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.

commands/perms.md · 13 lines

What it actually says

Use the permissions-helper skill for: $ARGUMENTS

Establish the rank ladder (groups + a track) before assigning nodes; scope per-world/per-server perks with contexts; set group weights for clean prefix resolution. Give the exact /lp … commands to run, in order. If a plugin's node names are uncertain, use learn-plugin-docs first — do not invent nodes.

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. yesterday First seen · 13 lines · 17 tokens per session scan A 1499180df481

Subscribe to this mod's changes

perms is a command published in the GitHub repository Teddy563/mcwrench (1 stars, last pushed 9d ago), licensed MIT. It adds 17 tokens to every session and 135 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-31.