User Management

User Management is a skill for Claude Code, Codex from agent0ai/space-agent. It costs 24 tokens per session (945 once invoked), scanned A, original, MIT.

Instructions for managing local accounts through each user's canonical files, including profile data, password records, sessions, and custom files.

In plain words
What is it for?
Use it to create, update, or remove users, change names, reset passwords, revoke sessions, and manage group membership files.
Why use it?
It explains where account data lives and how actions such as password resets or session revocation affect it.

Skill for Claude CodeCodex

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 skills/agent0ai/space-agent/user-management
Any agent
npx skills add agent0ai/space-agent --skill user-management
Clone the repo
git clone --depth 1 https://github.com/agent0ai/space-agent

Made for: Claude Code, Codex.

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 User Management

README.md
[![agentmods](https://agentmods.dev/badge/skills/agent0ai/space-agent/user-management.svg)](https://agentmods.dev/skills/agent0ai/space-agent/user-management)
Your own site
<a href="https://agentmods.dev/skills/agent0ai/space-agent/user-management"><img src="https://agentmods.dev/badge/skills/agent0ai/space-agent/user-management.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 945 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.00024 $0.00945
Opus 5 $0.00012 $0.00473
Sonnet 5 $0.00005 $0.00189
Haiku 4.5 $0.00002 $0.00094

Measured 4d ago against content hash 086bd2e36a4a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

User Management 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

app/L0/_all/mod/_core/admin/ext/skills/user-management/SKILL.md · 114 lines

How it starts

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

Use this skill when the user asks to create a user, remove a user, change a user's full name, reset a password, revoke sessions, or explain how user account files are organized.

Canonical User Tree

  • L2/<username>/ is the user's root folder. If this folder is deleted, the local account data and user customware are removed.
  • L2/<username>/user.yaml stores user metadata. full_name belongs here.
  • L2/<username>/meta/password.json stores the backend-sealed SCRAM verifier used by login.
  • L2/<username>/meta/logins.json stores signed session verifiers. Writing {} here revokes current sessions.
  • L2/<username>/mod/ is the optional user customware root.

There is no separate user registry file. The watched user index is derived from the files under L2/<username>/.

File API Rules

  • Create directories by writing a path that ends with /, for example await space.api.fileWrite("L2/alice/") or await space.api.fileWrite("L2/alice/mod/").
  • Delete files or directories with await space.api.fileDelete(path). Directory deletes are recursive.
  • Use await space.api.call("password_generate", { method: "POST", body: { password } }) to create a fresh sealed password record before writing meta/password.json.
  • Do not hand-roll meta/password.json or individual session entries. The backend secret must sign or seal them.
  • Use space.utils.yaml.parse() and space.utils.yaml.stringify() when editing user.yaml or group.yaml.

Common Operations

List users

Use await space.api.fileList("L2/", false). Each direct child directory is one user root.

Create a user

Use a single path-safe username segment such as alice or qa_bot. Then:

const username = "alice";
const fullName = "Alice Example";
const password = "replace-me";
const verifier = await space.api.call("password_generate", {
  method: "POST",
  body: { password }
});

return await space.api.fileWrite({
  files: [
    { path: `L2/${username}/` },
    { path: `L2/${username}/mod/` },
    {
      path: `L2/${username}/user.yaml`,
      content: space.utils.yaml.stringify({ full_name: fullName })
    },
    {
      path: `L2/${username}/meta/password.json`,
      content: `${JSON.stringify(verifier, null, 2)}\n`
    },
    {
      path: `L2/${username}/meta/logins.json`,
      content: "{}\n"
    }
  ]
});

Read the full file on GitHub · 114 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. 4d ago First seen · 114 lines · 24 tokens per session scan A 086bd2e36a4a

Subscribe to this mod's changes

User Management is a skill published in the GitHub repository agent0ai/space-agent (1,392 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 945 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens