Borrowing it
Nothing to install: this file belongs to silo-code/silo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/silo-code/silo/main/.agents/skills/verifier-gui/SKILL.mdgit clone --depth 1 https://github.com/silo-code/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/silo-code/silo/verifier-gui)<a href="https://agentmods.dev/skills/silo-code/silo/verifier-gui"><img src="https://agentmods.dev/badge/skills/silo-code/silo/verifier-gui/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/silo-code/silo/verifier-gui"><img src="https://agentmods.dev/badge/skills/silo-code/silo/verifier-gui.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.00097 | $0.04638 |
| Opus 5.5 | $0.00039 | $0.01855 |
| Sonnet 5.5 | $0.00019 | $0.00928 |
| Haiku 4.5 | $0.00010 | $0.00464 |
Grade C, and why
verifier-gui scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$WS_DIR" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`Bash` call.** The `silo()` helper is just `curl`; bash variables (`WS_ID`, How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Silo GUI Verifier
The handle the verify skill looks for: how to get the running Silo app under
control and capture evidence from it. Silo is a Tauri desktop app; its surface is
pixels + a dev-only RPC bridge. This skill drives that bridge.
It does not judge. It launches, drives, captures. The verdict is verify's.
Golden rule 1: verify in a sandbox workspace, never the user's
The app may be the user's live session with real workspaces and terminals. Do
all verification in a workspace you create from a temp dir, and delete it when
done. Never openTerminal/deleteWorkspace/openFile against an existing
workspace — you'd pollute or destroy real state. Create → activate → verify →
delete. This also makes destructive paths (workspace delete, session kill) safe
to exercise.
Golden rule 2: one turn, not one op per turn
The wall-clock cost here is agent turns, not the RPC bridge — each bridge call
is ~milliseconds on localhost, but every separate Bash tool call is a full model
round-trip (seconds). So issue a whole drive + capture sequence as a single
Bash call. The silo() helper is just curl; bash variables (WS_ID,
WS_DIR) persist within one invocation, so create → activate → drive →
screenshot → decode all belong in one block (see §2). A 6-step flow then costs
2 turns, not 7.
Only split into a separate turn when you genuinely must:
- The final
Read /tmp/silo.png—Readis its own tool, so capture-in-one-turn then read-in-the-next is the floor (2 turns). - Branching on an observed result — if the next op depends on what you saw (a count, a tab list, a pass/fail), end the block, read the output, then decide. A fixed setup sequence has no such dependency — never split it.
Echo any state you'll need next turn (e.g. echo "WS_ID=$WS_ID") — bash vars die
at the end of the Bash call.
1. Get the app up (attach or launch)
The bridge listens on 127.0.0.1:7878 (dev builds only — app:dev is built
--features automation). Define the request helper first — the contract is
strict: header X-Silo-Automation: 1 and a loopback Host, POST /, body
{"op", "args"}.
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 Changed · +1 lines dc1208e4b2bc
- 1mo ago First seen · 305 lines · 97 tokens per session scan C 8865ae751fb5
verifier-gui is a skill published in the GitHub repository silo-code/silo (62 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 4,638 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, 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
orca-emulator
This discovery stub loads the version-matched guide from the Orca executable used for this session.
verify-ui-change-in-cloud
Verifies user-facing Warp client changes by spawning a cloud agent with computer use to test Warp. Use only when the user explicitly requested computer-use verification or accepted an offer to run it, and ONLY in non-sandboxed environments and local environments. Triggers a cloud agent that runs the test-warp-ui skill.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
tui-test
Control, inspect, test, and record real terminal apps with the tui-test CLI or its Rust, Python, and JavaScript APIs. Use for shells, TUI apps, text and style locators, keyboard or mouse input, terminal state, clipboard waits, screenshots, recordings, snapshots, and live terminal sessions.
horizon-app-testing
Run or inspect declared iOS and Android native app tests through Horizon devicetestrun and app MCP tools. Use for App Automate sessions, native actions, evidence, and cleanup; desktop fixtures use horizon-device.
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.