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/silo-testing/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/silo-testing)<a href="https://agentmods.dev/skills/silo-code/silo/silo-testing"><img src="https://agentmods.dev/badge/skills/silo-code/silo/silo-testing/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/silo-testing"><img src="https://agentmods.dev/badge/skills/silo-code/silo/silo-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.00486 |
| Opus 5.5 | $0.00026 | $0.00194 |
| Sonnet 5.5 | $0.00013 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
silo-testing 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.
What it actually says
Testing in Silo
Every change that adds or changes behavior ships with unit tests in the same
change. Tests are part of the work, not a follow-up. Don't mark a task done
until pnpm test is green with coverage for what you added.
How testing works here:
- Vitest, co-located. Put
*.test.ts/*.test.tsxnext to the source it covers; the packagevitest.config.tspicks upsrc/**/*.{test,spec}.{ts,tsx}. Run everything withpnpm test, or one package withpnpm --filter <pkg> exec vitest run <path>. - Pure-logic style. The suite tests logic, not rendered React
(
@testing-library/reactis intentionally not a dependency). When the logic you're adding lives inside a component, extract it into a pure, exported helper and test that — e.g.view-switcher-model.ts(switcher show/segmented/ dropdown rules),markdown-preview/menu.ts(context-menu enablement), andmarkdown-preview/match.ts(file matching) were factored out of their components precisely so the rules are unit-testable. Components stay thin glue. - Host state can be driven directly: set up
store(the valtio proxy) and the relevant registries inbeforeEach, exercise the service, assert on the store — seeeditor-service.test.tsandeditor-registry.test.ts. - Cover the contract and the edges, not just the happy path: fallbacks,
no-ops/guards, disabled states, and "hidden/absent" cases (the editor
view-switching tests pin the priority tie-break, stale-
viewTypefallback, read-only Cut/Paste, and the single-view/diff/untitled hidden cases).
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 · 32 lines · 65 tokens per session scan A b2ade918a5f2
silo-testing is a skill published in the GitHub repository silo-code/silo (62 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 486 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
orca-emulator
This discovery stub loads the version-matched guide from the Orca executable used for this session.
test-value
Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes before a commit or PR. Keep ordinary implementation and pre-commit use scoped to the affected behavior, not a repository-wide audit.
verify
Verify that a change really works before you claim completion.
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.
cmux-test-bisect
Find when and why tests broke on main: bisect a Swift package suite on CI across old commits, read the failure matrix, and decide per test whether the test went stale or the code regressed. Use when a suite is red on main, when PR CI only ran filtered tests and the full suite has drifted, or when asked which PR broke…