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/silo-code/silo/docs-screenshotnpx skills add silo-code/silo --skill docs-screenshotgit clone --depth 1 https://github.com/silo-code/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.00040 | $0.02978 |
| Opus 5 | $0.00020 | $0.01489 |
| Sonnet 5 | $0.00008 | $0.00596 |
| Haiku 4.5 | $0.00004 | $0.00298 |
Grade A, and why
docs-screenshot scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
silo(){ curl -s -m30 -X POST http://127.0.0.1:7878/ \ How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Silo Docs Screenshot
Produces a 600×400 PNG of a Silo UI region composited over the standard orange/purple
wallpaper (apps/docs/public/img/wallpaper.jpg), styled as a windowed screenshot floating
on the desktop — consistent with every other image in the guide.
Quick reference
Corner Desktop visible Window bleeds Window canvas pos Merged geometry Round corner
────────── ───────────────── ─────────────── ───────────────────── ─────────────────── ────────────
top-left top(65) left(80) right, bottom (80, 65) +40+30 all 4
bot-left bot(10) left(80) top, right (80, 0) +40+-35 bot-left only
top-right top(65) right(80) left, bottom (520-OW, 65) +(480-OW)+30 top-right only
bot-right bot(10) right(80) top, left (520-OW, 390-OH) +(480-OW)+(355-OH) bot-right only
center all sides ~50px none ((600-OW)/2, (400-OH)/2) +((600-OW)/2-40)+((400-OH)/2-35) all 4
top-left — top half of app, feature on the LEFT (e.g. workspaces panel, editor).
bot-left — bottom of app, feature on the LEFT (e.g. status bar menu).
top-right — top half of app, feature on the RIGHT (e.g. file explorer, right side panel).
bot-right — bottom of app, feature on the RIGHT (e.g. right-side status items, output panel).
Pipeline
1. Take the screenshot
silo(){ curl -s -m30 -X POST http://127.0.0.1:7878/ \
-H 'X-Silo-Automation: 1' -H 'Content-Type: application/json' \
--data "$1"; }
# Set up any app state first (open panels, menus, etc.), then:
silo '{"op":"screenshot"}' > /tmp/shot.json
python3 -c "
import json,base64
d=json.load(open('/tmp/shot.json'))
r=d['result']
open('/tmp/silo.png','wb').write(base64.b64decode(r['png_base64']))
print(r['width'], r['height'])
"
# Typical output: 3024 1898 (2× retina — logical pixels are half)
2. Choose your crop
The source is 3024×1898 at 2× retina (logical: 1512×949).
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.
- yesterday First seen · 203 lines · 40 tokens per session scan A 797786c9ca09
docs-screenshot is a skill published in the GitHub repository silo-code/silo (53 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 2,978 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
agtx-execute
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
agtx-plan
Plan a task implementation. Analyze the codebase, create a detailed plan, write it to .agtx/plan.md, then stop and wait for user approval before making any changes.
agtx-research
Explore the codebase to understand a task before planning. Write findings to .agtx/research.md and stop. This is a read-only exploration — do not modify any files.
agtx-brainstorm
Enter brainstorm mode to explore a feature or enhancement idea. Stays in discussion mode only — no planning, no implementation. Use /agtx:sweep when ready to push outcomes to the board.
agtx-review
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.