Space Agent is a browser-based agent workspace that can build pages, tools, widgets, and workflows directly into the running interface. It is for users who want an extensible personal or collaborative assistant whose capabilities can grow through modular pieces and text-based skills. Catalogue add-ons extend the agent's skills and workflows.
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.
npx skills add agent0ai/space-agent --skill groupsgit clone --depth 1 https://github.com/agent0ai/space-agentWrote 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.
[](https://agentmods.dev/skills/agent0ai/space-agent/groups)<a href="https://agentmods.dev/skills/agent0ai/space-agent/groups"><img src="https://agentmods.dev/badge/skills/agent0ai/space-agent/groups/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.
<a href="https://agentmods.dev/skills/agent0ai/space-agent/groups"><img src="https://agentmods.dev/badge/skills/agent0ai/space-agent/groups.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00024 | $0.00860 |
| Opus 5.5 | $0.00010 | $0.00344 |
| Sonnet 5.5 | $0.00005 | $0.00172 |
| Haiku 4.5 | $0.00002 | $0.00086 |
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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Admin Groups — 100% identical, 0 lines differ
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.yamlis 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
_allis the implicit everyone group.- Do not create or rely on
L1/_all/group.yamlfor membership._allmembership is universal, not file-driven. _adminis the admin group.- Adding a user or included group to
_adminmakes those users admins.
Canonical group.yaml Fields
included_usersincluded_groupsmanaging_usersmanaging_groups
Meaning:
included_users: direct members of the groupincluded_groups: groups whose members also become members of this groupmanaging_users: users who may write this group'sL1/<group>/treemanaging_groups: groups whose members may write this group'sL1/<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));
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.
- 1mo ago First seen · 117 lines · 24 tokens per session scan A 7dfed573d4d3
Admin Groups is a skill published in the GitHub repository agent0ai/space-agent (1,411 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 860 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…