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 developmentgit 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/development)<a href="https://agentmods.dev/skills/binary16labs/prime-silo/development"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/development/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/binary16labs/prime-silo/development"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/development.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00784 |
| Opus 5.5 | $0.00010 | $0.00314 |
| Sonnet 5.5 | $0.00005 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
Development 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.
This is a copy
100% identical to Development — 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this skill when the user asks how to build a module, where code should live, how layers work, or how the extension/component/Alpine runtime composes the frontend.
Layer Model
L0is firmware. Repo-owned first-party code belongs here.L1is group customware. Use it for group-level overrides and additions.L2is user customware. Use it for per-user overrides and additions.- First-party source for this repository should normally live under
app/L0/_all/mod/_core/.... L1andL2are runtime state, not the home for durable repo-owned product code.
Module Layout
- Browser modules are namespaced as
mod/<author>/<repo>/.... - A first-party module usually lives at
app/L0/_all/mod/_core/<feature>/. - Keep real implementation files in the module folder.
- Keep
ext/html/adapter files andext/js/hook files thin. They should usually mount a real component or provide a focused hook, not hold the whole feature.
How The Frontend Composes
- Page shells in
server/pages/stay thin and expose<x-extension id="...">anchors. - Matching HTML extension files live under
mod/<author>/<repo>/ext/html/<anchor>/.... - Those extension files usually mount a real component with
<x-component path="/mod/...">. <x-component>loads the component HTML, styles, scripts, and nested components.- Alpine stores and small module utilities own the behavior.
Example pattern:
<x-extension id="page/admin/body/start"></x-extension>
<x-component path="/mod/_core/admin/views/shell/shell.html"></x-component>
Alpine And Store Pattern
- Component HTML owns structure and bindings.
- Stores created through
space.fw.createStore(...)own state, async work, persistence, and API calls. - Small utility modules own parsing and rendering helpers.
- Do not move large feature logic into long inline
x-datablocks.
JS Extension Hooks
- Use
space.extend(import.meta, async function name(...) { ... })for behavioral extension seams. /starthook files run before the wrapped function./endhook files run after the wrapped function.- JS hook files live under
mod/<author>/<repo>/ext/js/<extension-point>/.... - Use HTML anchors for structural seams and
space.extend(...)for behavioral seams.
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 · 75 lines · 25 tokens per session scan A 869ef286b786
Development is a skill published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 784 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to Development, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
xh
Use when the agent or user needs to make an HTTP request from the shell - GET a URL, POST JSON to an API, check a webhook with auth, test a REST endpoint, fetch and inspect headers, or upload a file.
dingtalk_channel_connect
Use a headed browser to automatically complete DingTalk channel integration for QwenPaw. Applicable when the user mentions DingTalk, developer console, Client ID, Client Secret, bot, Stream mode, binding or configuring a channel. Supports pausing when a login page is detected and resuming after the user logs in.
dingtalk_channel_connect
A browser-based procedure for connecting a QwenPaw bot to DingTalk, a workplace messaging platform. It covers creating or configuring the application and publishing the finished bot.
browser_cdp
Use this skill when the user explicitly wants to connect to a running Chrome browser, scan local CDP ports, specify a cdpport, or share a single browser across multiple agents/tools. By default browser opens no debugging port; pass an explicit cdpport only when the user wants another local tool to attach.
browser_cdp
Browser connection controls for finding local debugging ports, attaching to an already running Chrome browser, or sharing one browser between tools.
browser_visible
Browser launch controls for choosing whether a Chromium-based browser window is visible, which browser program to run, and which startup options to pass.