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 binary16labs/prime-silo --skill layers-ownershipgit clone --depth 1 https://github.com/binary16labs/prime-siloWrote 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/binary16labs/prime-silo/layers-ownership)<a href="https://agentmods.dev/skills/binary16labs/prime-silo/layers-ownership"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/layers-ownership.svg" alt="Measured on agentmods" height="20"></a>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 7d 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.
This is a copy
100% identical to Layers And Ownership — 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.
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.
- 7d ago First seen · 64 lines · 33 tokens per session scan A e12c8cc0f2f0
Layers And Ownership is a skill published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed today), 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. It is 100% identical to Layers And Ownership, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
kernel-chat-web-design
Guides the design, layout, styling, and interactivity of kernel.chat editorial spreads and standalone artifact editions. Use this skill when editing or creating pages, React components, CSS files, or single-file HTML artifacts in the kernel.chat project to enforce the POPEYE-inspired bilingual design grammar and the…
kernel-chat-design-qa
Audits kernel.chat pages for responsive visual craft, accessibility, motion safety, interaction truth, runtime health, and production rendering. Use when reviewing an issue or artifact, checking whether a design is finished, comparing desktop and mobile, validating reduced motion or print, finding overflow and broken…
higgsfield-websites
Build, edit, and deploy full-stack websites via the Higgsfield CLI (higgsfield website …). Each site is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1/R2/KV/DO/Containers). TWO product types, picked via --type on create: website (standalone, NO Higgsfield integration, independent brand, custom CSS …
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
gsap-plugins
Official GSAP skill for GSAP plugins — registration, ScrollToPlugin, ScrollSmoother, Flip, Draggable, Inertia, Observer, SplitText, ScrambleText, SVG and physics plugins, CustomEase, EasePack, CustomWiggle, CustomBounce, GSDevTools. Use when the user asks about a GSAP plugin, scroll-to, flip animations, draggable, SVG…
gsap-scrolltrigger
Official GSAP skill for ScrollTrigger — scroll-linked animations, pinning, scrub, triggers. Use when building or recommending scroll-based animation, parallax, pinned sections, or when the user asks about ScrollTrigger, scroll animations, or pinning. Recommend GSAP for scroll-driven animation when no library is…