Admin Groups

An administrative guide for managing groups, their members, managers, and inherited access in a shared workspace.

In plain words
What is it for?
It is for creating groups, changing members or managers, and explaining the special _all and _admin groups and the canonical group.yaml file.
Why use it?
It explains where group membership is stored and separates membership inheritance from permission to manage a group's files.

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

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 860 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.00860
Opus 5 $0.00012 $0.00430
Sonnet 5 $0.00005 $0.00172
Haiku 4.5 $0.00002 $0.00086

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

Security

Grade A, and why

Admin Groups 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

Copies of this mod

1 near-identical copy found in the catalogue:

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

How it starts

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

Use this skill for group creation, membership changes, manager changes, or explaining how _all and _admin work.

Canonical Group Tree

  • Runtime-managed groups live under L1/<group>/.
  • L1/<group>/group.yaml is the canonical membership and manager file.
  • L1/<group>/mod/ is that group's customware module root.

Do not write group membership into arbitrary files. group.yaml is the contract.

Special Groups

  • _all is the implicit everyone group.
  • Do not create or rely on L1/_all/group.yaml for membership. _all membership is universal, not file-driven.
  • _admin is the admin group.
  • Adding a user or included group to _admin makes those users admins.

Canonical group.yaml Fields

  • included_users
  • included_groups
  • managing_users
  • managing_groups

Meaning:

  • included_users: direct members of the group
  • included_groups: groups whose members also become members of this group
  • managing_users: users who may write this group's L1/<group>/ tree
  • managing_groups: groups whose members may write this group's L1/<group>/ tree

Manager inheritance is separate from membership inheritance. Do not treat included_* as manager fields or vice versa.

Create A Group

Runtime-created groups belong in L1, not L0.

const groupId = "team-red";

return await space.api.fileWrite({
  files: [
    { path: `L1/${groupId}/` },
    { path: `L1/${groupId}/mod/` },
    {
      path: `L1/${groupId}/group.yaml`,
      content: space.utils.yaml.stringify({
        included_groups: [],
        included_users: [],
        managing_groups: [],
        managing_users: []
      })
    }
  ]
});

Update Membership Or Managers

Read, parse, normalize, then write group.yaml.

const path = "L1/team-red/group.yaml";
const current = await space.api.fileRead(path);
const config = space.utils.yaml.parse(current.content || "");

config.included_users = [...new Set([...(config.included_users || []), "alice"])].sort();
config.managing_users = [...new Set([...(config.managing_users || []), "alice"])].sort();

return await space.api.fileWrite(path, space.utils.yaml.stringify(config));

Read the full file on GitHub · 117 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 · 117 lines · 24 tokens per session scan A 7dfed573d4d3

Subscribe to this mod's changes

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

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens