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 layers-ownershipgit 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/layers-ownership)<a href="https://agentmods.dev/skills/agent0ai/space-agent/layers-ownership"><img src="https://agentmods.dev/badge/skills/agent0ai/space-agent/layers-ownership.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 23 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00033 | $0.00688 |
| Opus 5 | $0.00016 | $0.00344 |
| Sonnet 5 | $0.00007 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
Layers And Ownership 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 8d 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:
- Layers And Ownership — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this skill before deciding where new files belong or how readable and writable content resolves across users and groups.
The Three Layers
L0is firmware. Repo-owned first-party code belongs here.L1is group customware. It is writable only for group managers and admins.L2is user customware. It is writable only for that user and admins.
Group And User Structure
L1/_allis the shared group layer available to everyone.L1/_adminis the admin group layer.L2/<username>/user.yamlstores user metadata such asfull_name.L2/<username>/meta/holds auth state such as password and login session records.L2/<username>/mod/is that user's customware module root.L1/<group>/group.yamlis the canonical group membership and management file.- When
CUSTOMWARE_GIT_HISTORYis enabled, each writableL1/<group>/andL2/<username>/root may have a server-managed local Git history repository. - L2 history ignores
meta/password.jsonandmeta/logins.json; rollback preserves those current auth files and keeps previous heads listable for forward travel when possible, while revert creates a new inverse commit.
Permission Model
- Nobody writes
L0. - Users may read their own
L2/<username>/. - Users may read
L0/<group>/andL1/<group>/for groups they belong to. - Users may write
L1/<group>/only when they manage that group directly or through a managing-group include chain. _adminmembers may write anyL1/andL2/path.
Group Config Fields
group.yaml uses these canonical fields:
included_usersincluded_groupsmanaging_usersmanaging_groups
Resolution Order
Readable module and extension resolution is rank-based:
L0/_all- readable
L0/<group>entries in group order L1/_all- readable
L1/<group>entries in group order L2/<username>
Higher-ranked exact same module-relative paths override lower-ranked ones. Different filenames under the same extension point compose together.
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.
- 8d ago First seen · 64 lines · 33 tokens per session scan A e12c8cc0f2f0
Layers And Ownership is a skill published in the GitHub repository agent0ai/space-agent (1,393 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 688 once invoked, about $0.0002 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.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…
vite
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.