Admin Users

An administration guide for managing user accounts, passwords, login sessions, and each user's stored files.

In plain words
What is it for?
Use it to create, update, or remove accounts, generate password records, revoke sessions, and work with user-specific storage.
Why use it?
It explains how users and their security records are represented and sets checks that prevent non-administrators from changing them incorrectly.

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/binary16labs/prime-silo/users
Any agent
npx skills add binary16labs/prime-silo --skill users
Clone the repo
git clone --depth 1 https://github.com/binary16labs/prime-silo

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 959 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00028 $0.00959
Opus 5 $0.00014 $0.00479
Sonnet 5 $0.00006 $0.00192
Haiku 4.5 $0.00003 $0.00096

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

Security

Grade A, and why

Admin Users 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 2d 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

This is a copy

100% identical to Admin Users — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

app/L0/_admin/mod/_core/overlay_agent/ext/skills/admin-user-management/users/SKILL.md · 130 lines

How it starts

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

Use this skill for concrete user-account work.

First Check

  • Call const info = await space.api.userSelfInfo().
  • Confirm info.groups.includes("_admin") === true.
  • Prefer logical app paths derived from the standard layer rules, not guessed disk paths.

Canonical User Tree

  • L2/<username>/ is the user's logical root.
  • L2/<username>/user.yaml stores user metadata such as full_name.
  • L2/<username>/meta/password.json stores the backend-sealed SCRAM verifier.
  • L2/<username>/meta/logins.json stores signed session verifiers.
  • L2/<username>/mod/ is that user's customware module root.

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

Path Rules

  • Use logical paths such as L2/alice/user.yaml.
  • When writable storage is relocated under CUSTOMWARE_PATH, these logical paths stay the same.
  • fileWrite(".../") creates a directory because the path ends with /.
  • Do not hand-craft meta/password.json or individual session entries. Use password_generate for password records and only write {} when revoking sessions.

Create A User

Use a normalized username segment such as alice, ops_bot, or qa-team-1.

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"
    }
  ]
});

Update User Metadata

Read user.yaml, parse it, mutate the fields you need, and write it back.

const path = "L2/alice/user.yaml";
const current = await space.api.fileRead(path);
const config = space.utils.yaml.parse(current.content || "");
config.full_name = "Alice Example";
return await space.api.fileWrite(path, space.utils.yaml.stringify(config));

Read the full file on GitHub · 130 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. 2d ago First seen · 130 lines · 28 tokens per session scan A 966df9494a2a

Subscribe to this mod's changes

Admin Users is a skill published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 959 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Admin Users, differing in 0 lines, and is treated as a copy.