settings

settings is a command for Claude Code from Beezi-AI/beezi-claude-plugin. It costs 0 tokens per session (8,647 once invoked), scanned A, original, Apache-2.0.

A settings command for the Beezi plugin. It can show or change rules, folders, account and plan details, crash-report choices, and the status line.

In plain words
What is it for?
It is for viewing or changing Beezi preferences, adding folders, checking account or plan information, and managing crash reports and status-line settings.
Why use it?
It gives users one place to manage plugin settings without manually inspecting configuration files. It also prevents sensitive tokens from being displayed.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the beezi plugin — 1 skill, 6 commands, 9 hooks, 1 MCP server shipped together

Good fit It is for viewing or changing Beezi preferences, adding folders, checking account or plan information, and managing crash reports and status-line settings.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Beezi-AI/beezi-claude-plugin
Claude Code
/plugin install beezi

Made for: Claude Code.

Or install beezi, the plugin that ships this one along with the rest of its 1 skill, 6 commands, 9 hooks, 1 MCP server.

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 settings

README.md
[![agentmods](https://agentmods.dev/badge/commands/beezi-ai/beezi-claude-plugin/settings/github.svg)](https://agentmods.dev/commands/beezi-ai/beezi-claude-plugin/settings)
Your own site
<a href="https://agentmods.dev/commands/beezi-ai/beezi-claude-plugin/settings"><img src="https://agentmods.dev/badge/commands/beezi-ai/beezi-claude-plugin/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 settings

Your own site · 80×15
<a href="https://agentmods.dev/commands/beezi-ai/beezi-claude-plugin/settings"><img src="https://agentmods.dev/badge/commands/beezi-ai/beezi-claude-plugin/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 8,647 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.00000 $0.08647
Opus 5.5 $0.00000 $0.03459
Sonnet 5.5 $0.00000 $0.01729
Haiku 4.5 $0.00000 $0.00865

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

Security

Grade A, and why

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 9d 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.

plugins/beezi/commands/settings.md · 549 lines

How it starts

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

Do NOT read, open, or inspect any files. Never echo any token.

Arguments: $ARGUMENTS

The user cannot see tool output: Claude Code collapses it after a few lines. A script's output reaches the user only through your reply text or a question's preview, so output you are told to show is copied VERBATIM into your reply, as its very first text: exactly as printed, never summarized, paraphrased, reformatted or replaced by a sentence of your own ("I've noted…" is wrong). Machine lines (key=value lines, and every line of an output you are told not to show) are never shown.

Previews: whenever a single-select question below says "with previews", give EVERY option a preview holding the named script output, copied exactly (a markdown table stays a table). The preview is what the user reads while choosing, so never leave it out.

AskUserQuestion, everywhere below: at most 4 questions in one call and at most 4 options in one question; multiSelect: true only with 2 or more options. Make one AskUserQuestion call per message and wait for its answers before the next (two calls in one message show the user only the last). A dismissed question runs nothing.

Read the settings: one command

Everything this command reads comes from ONE command, picked by the first word of the arguments. Run it once, first, and take everything below from its output: never run a read again, nor another script to read settings. The commands below only change settings or refresh the plan.

First word of the arguments Run EXACTLY
show alone node ${CLAUDE_PLUGIN_ROOT}/scripts/settings.mjs all
rules node ${CLAUDE_PLUGIN_ROOT}/scripts/settings.mjs rules
new-folders node ${CLAUDE_PLUGIN_ROOT}/scripts/settings.mjs new-folders
account node ${CLAUDE_PLUGIN_ROOT}/scripts/settings.mjs account
telemetry or statusline, alone or + show node ${CLAUDE_PLUGIN_ROOT}/scripts/settings.mjs privacy
telemetry <mode> or statusline on/off nothing: go to Crash reports & status line
statusline badge on/off nothing: go to Crash reports & status line
refresh nothing: go to Refresh my Claude plan
undo nothing: run node ${CLAUDE_PLUGIN_ROOT}/scripts/workspace.mjs undo and write its first line verbatim; stop
nothing, or anything else node ${CLAUDE_PLUGIN_ROOT}/scripts/settings.mjs

Its output is blocks, each from a <name …> line to its </name> line:

  • <show> — always first. Write its lines (not the tag lines) verbatim as your reply's first text.
  • <keys> — for you only:
    • menu=<label>|<label>… — the sections that apply here;
    • one line per linked account: account=<key> default=<yes|no> multi=<yes|no> workspaces=<n> status=<…> email=<email> (multi=yes: the account is in several workspaces; workspaces=<n> is its known workspace count, 0 when not known yet; no such line: nothing is linked);
    • crash=<correlate|on|anonymous|off> statusline=<on|off> badge=<on|off>.
  • <labels> — with no arguments only: one line per menu= label, in the same order, the label with its current state (e.g. Rules: here → Acme, New folders: ask me, Account: 2 linked); these are the menu question's option labels.
  • <rules account="<key>"> — one per account whose workspaces are known (with no arguments, or rules); see Rules.
  • <here-card account="<key>"> — one per such account when this folder is known (with no arguments, or rules): where you are and where its analytics go now; a preview for Rules.
  • <new-folders account="<key>"> — one per account in several workspaces (with no arguments, or new-folders); see New folders.
  • <preview section="<label>"> — one per menu section (with no arguments only).

Read the full file on GitHub · 549 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. 9d ago Changed · +65 lines 93a24bc29adf
  2. 23d ago First seen · 484 lines · 0 tokens per session scan A bbdb119002a0

Subscribe to this mod's changes

settings is a command published in the GitHub repository Beezi-AI/beezi-claude-plugin (63 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 8,647 tokens. 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-15.

Related

settings compared with commands from other repositories

settings next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
settingsBeezi-AI/beezi-claude-pluginCommand639d agoApache-2.0A0Claude Code
huntsoheilfallah/jobxhunterCommand92mo agoMITA20Claude Code
cc-probeline-configlabzink/cc-probelineCommand122mo agoMITA21Claude Code
orchestrateegorfedorov/claude-context-optimizerCommand13010d agoMITA0Claude Code
todo.templateevan043/claude-cli-advanced-starter-packCommand613mo agoMITA0Claude Code
clean-checkTeamManagementPlugin/claude-pluginCommand623d agoMITA27Claude Code
notessystemoperators/claude-pluginsCommand63d agoMITA6Claude Code