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 agentmods add skills/binary16labs/prime-silo/modules-routingnpx skills add binary16labs/prime-silo --skill modules-routinggit clone --depth 1 https://github.com/binary16labs/prime-siloWhat 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 | $0.00028 | $0.01188 |
| Opus 5 | $0.00014 | $0.00594 |
| Sonnet 5 | $0.00006 | $0.00238 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
Modules And Routing 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.
This is a copy
100% identical to Modules And Routing — 6 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this skill when creating or updating routed modules, deciding where files belong, or wiring a feature into the authenticated app shell.
If the user wants a reusable app surface, tool UI, settings panel, or workflow screen, prefer a custom routed page module over a space. Spaces are for persisted user-authored widget canvases; custom pages are for feature-owned interfaces.
First-Party Module Placement
- Browser modules are namespaced as
mod/<author>/<repo>/.... - Repo-owned first-party modules should normally live under
app/L0/_all/mod/_core/<feature>/. - A routed feature should usually own its own
view.htmlunder that module root. - Keep the module root as the real implementation location and use
ext/html/...files only as thin adapters into existing seams.
Custom Pages Instead Of Spaces
- Build a custom routed page when the extension should behave like a first-class feature screen instead of a widget on a persisted space canvas.
- Use spaces when the user wants a configurable board of widgets that lives under
~/spaces/.... - Use a routed page when the feature owns its own layout, state, and navigation flow.
- To make a custom page appear in the dashboard
Panelssection, addext/panels/<name>.yamlin the owning module. - Panel manifests should define
name,path, optionaldescription, optionalicon, and optionalcolor. - For first-party
_coreroutes, the manifestpathmay use shorthand such asuserinstead of a full/mod/...path. - Panel manifest
pathvalues may use shorthand route paths such asuser, prefixed hash paths such as#/user, or direct/mod/...HTML paths such as/mod/_core/user/view.html.
Router Resolution
- The main app is hash-routed.
#/dashboardresolves to/mod/_core/dashboard/view.html.#/time_travelresolves to/mod/_core/time_travel/view.html.- A multi-segment route such as
#/author/repo/pathresolves to/mod/author/repo/path/view.html. - If the final route segment already ends in
.html, the router resolves directly to that file under/mod/.... - Query parameters stay attached to the resolved route target.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 122 lines · 28 tokens per session scan A fdc2ca3b66ab
Modules And Routing is a skill published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 1,188 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Modules And Routing, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
draw-image
Generate an image from a text prompt using an OpenAI-compatible image generation API (gpt-image-1-mini or compatible). The image is uploaded to the gofile.io public file sharing service and ONLY the public download page URL is returned. Trigger when user asks to draw, paint, generate, or create an image.
compose:subagent
Use when executing implementation plans with independent tasks in the current session.
compose:worktree
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.
compose:merge
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
compose:new-skill
Use when creating new skills or editing existing skills for the project or personal skill library.
compose:plan
Use when you have a spec or requirements for a multi-step task, before touching code.