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/backend-referencenpx skills add binary16labs/prime-silo --skill backend-referencegit 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.00029 | $0.01470 |
| Opus 5 | $0.00015 | $0.00735 |
| Sonnet 5 | $0.00006 | $0.00294 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
Backend Reference 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 Backend Reference — 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this skill when frontend work depends on understanding backend behavior. This skill is read-only context, not authorization to change backend files.
Hard Boundary
- Do not edit
server/,commands/, orpackaging/from this skill set. - If the task truly requires backend changes, stop and ask instead of treating this skill as permission.
- Backend changes are non-standard in this project. Only ask for them when frontend-only work cannot safely enforce security, integrity, cross-user isolation, or runtime stability.
- When you ask, explain why the frontend solution would be insufficient and describe the narrow backend change required.
Page And Request Flow
Current request order is:
- API preflight handling
/api/proxy/api/<endpoint>/mod/.../~/...and/L0/...,/L1/...,/L2/...- page shells and page actions
The browser app mounts through page shells in server/pages/. /login is public. / and /admin require authentication.
API Families
Important frontend-facing endpoint families are:
- app files:
file_list,file_paths,file_read,file_write,file_delete,file_copy,file_move,file_info,folder_download - local history:
git_history_list,git_history_diff,git_history_preview,git_history_rollback,git_history_revert - modules:
module_list,module_info,module_install,module_remove - runtime and identity:
extensions_load,password_generate,password_change,user_crypto_session_key,user_self_info
These endpoints are thin wrappers over shared helpers in server/lib/customware/ and server/lib/auth/.
file_write still defaults to whole-file replacement, but it also supports operation: "append", "prepend", and "insert". Insert writes accept exactly one anchor through line, before, or after, use the first literal before or after match, treat line as a 1-based insertion point, and require utf8.
file_list and file_paths support access: "write" or writableOnly: true for writable-only discovery. They also support gitRepositories: true; with a pattern such as **/.git/, file_paths returns local-history owner roots like L1/team/ and L2/alice/ without exposing reserved .git metadata paths.
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 · 84 lines · 29 tokens per session scan A 0137fc83f230
Backend Reference is a skill published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed 9d ago), licensed MIT. It adds 29 tokens to every session and 1,470 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 Backend Reference, differing in 0 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: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:plan
Use when you have a spec or requirements for a multi-step task, before touching code.
compose:report
Use after implementation is verified and before merge — consolidates multiple spec iterations into a single final-state report, marks related specs, and records key lessons.
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.