Borrowing it
Nothing to install: this file belongs to vorn-run/vorn. 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/vorn-run/vorn/main/.claude/skills/vorn-wp-builder/SKILL.mdgit clone --depth 1 https://github.com/vorn-run/vornWrote 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/vorn-run/vorn/vorn-wp-builder)<a href="https://agentmods.dev/skills/vorn-run/vorn/vorn-wp-builder"><img src="https://agentmods.dev/badge/skills/vorn-run/vorn/vorn-wp-builder/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/vorn-run/vorn/vorn-wp-builder"><img src="https://agentmods.dev/badge/skills/vorn-run/vorn/vorn-wp-builder.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.00051 | $0.01509 |
| Opus 5.5 | $0.00020 | $0.00604 |
| Sonnet 5.5 | $0.00010 | $0.00302 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
vorn-wp-builder 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Ghostty's `build.zig.zon` files with curl and `zig fetch <file>`; for How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building a native core work package
Your brief gives the work package a spec with four fields. Treat them as the contract:
| Field | What it means for you |
|---|---|
| Read | Every file and design-note section listed. Read them all before writing code. |
| Must pass | The tests that decide acceptance. Each test id it names is a test you write. |
| Depends on | Check it is merged on main. If not, build stacked and keep the PR a draft. |
| Done when | The definition of done. Check every item before you open the PR for review. |
Design notes define shared terms (records, cursors, offsets); use their names in code.
1. Orient
- Read the spec and every linked section. Note each must-pass test id.
- Find the code being changed and every test that covers it (the crate's
tests/,crates/vornd/tests/,tests/*.test.ts). Those tests become your acceptance suite. - Read the existing crates (
packages/core/crates/*) and how the nearest finished one is wired into vornd or vorn-app. Reuse their shapes.
2. Design the crate API first
- New logic goes in a plain crate under
packages/core/crates/<name>(packagevorn-<name>), added to the workspacemembers. No tokio unless the logic itself is concurrent. - Write the public API as types and signatures with
///docs before the bodies: what it owns, what it borrows, what can fail (an error enum), what isSend. - Keep the API in the vocabulary of the design notes (record, cursor, epoch, checkpoint).
3. Implement with tests
- Unit tests in the crate (
#[cfg(test)] mod tests) for logic and edge cases; integration tests incrates/<name>/tests/for the public API only. - Property tests (seeded) for anything with a round-trip or an invariant, especially the test ids that say "property". Keep the failing seeds as regression cases.
- Criterion benches in
crates/<name>/benches/when the spec has a number. - Apply the
rust-idiomsskill throughout.
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.
- 7d ago Changed · -2 lines · +4 tokens per session 37f1c705d708
- 11d ago Changed · -23 lines f5bc9121a944
- 15d ago Changed · +10 lines ccc73a2270b4
- 19d ago Changed 92d1d96f2ed0
- 22d ago Changed · +4 lines 561cd1e81426
- 23d ago Changed 013c7414254e
- 24d ago First seen · 137 lines · 47 tokens per session scan A 838807aaf2d7
vorn-wp-builder is a skill published in the GitHub repository vorn-run/vorn (25 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,509 once invoked, about $0.0002 per session on Opus 5.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-10-05.
Other skills, from other repositories
template-instantiation
Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…
rust-engineer
Acquire expert Rust developer specialisation in rust systems programming, memory safety, and zero-cost abstractions. Masters ownership patterns, async programming, and performance optimisation for mission-critical applications.
rust-development
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
rust-development
You MUST activate this skill when working on Rust projects.
neo-rust
Use this skill when writing, refactoring, debugging, or auditing Rust code. Trigger for .rs files, Cargo projects, ownership/borrowing/lifetime issues, Result/Option error handling, unnecessary clone/performance work, unsafe code review, or modern Rust architecture.
raspberry-pi-rust-embedded
Production-grade embedded Rust guidelines for Raspberry Pi (bare-metal nostd and Linux embedded std/rppal/embedded-hal). Use when developing low-latency hardware control apps, embedded Rust drivers, Linux GPIO/SPI/I2C/UART software, real-time interrupt handlers, and memory-safe hardware abstractions.