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/veryfront/veryfront-code/vf-module-developmentnpx skills add veryfront/veryfront-code --skill vf-module-developmentgit clone --depth 1 https://github.com/veryfront/veryfront-codeWhat 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.00037 | $0.01106 |
| Opus 5 | $0.00018 | $0.00553 |
| Sonnet 5 | $0.00007 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
vf-module-development 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Veryfront Module Development
Overview
Veryfront has 45+ modules in src/, organized in strict dependency layers. Each module has a clear public API via barrel exports.
Core principle: Modules communicate through their public API. Never import from another module's internals.
Dependency Layers
Layer 5 (top): Orchestrators → server/, proxy/, build/, cli/
Layer 4: Features → data/, html/, react/, rendering/
Layer 3: Module System → modules/, transforms/, cache/
Layer 2: Infrastructure → security/, routing/, middleware/
Layer 1 (bottom): Foundation → config/, types/, utils/, errors/, platform/
Rules:
- A module may only import from its own layer or lower layers
- Never import upward (e.g., Foundation must not import from Features)
- Validate with:
deno task validate:architecture
Module Structure
src/my-module/
├── index.ts # Public API (barrel exports only)
├── index.test.ts # Export verification test
├── types.ts # Public types and interfaces
├── implementation.ts # Core logic
├── factory.ts # Factory functions (if needed)
├── utils.ts # Module-internal utilities
└── sub-feature/ # Sub-directories for complex modules
├── index.ts
└── implementation.ts
Hash Imports
All internal imports use hash-based aliases defined in deno.json:
// Correct
import { VeryfrontError } from "#veryfront/errors";
import { defineConfig } from "#veryfront/config";
import { logger } from "#veryfront/utils/logger";
// Wrong - never use relative paths across modules
import { VeryfrontError } from "../../errors/types.ts";
Within the same module, use relative imports:
// Within src/my-module/
import { MyType } from "./types.ts";
import { helper } from "./utils.ts";
Barrel Exports (index.ts)
Every module's index.ts is its public API:
// src/my-module/index.ts
// Re-export public types
export type { MyConfig, MyOptions } from "./types.ts";
// Re-export public functions/constants
export { createMyThing } from "./factory.ts";
export { MY_ERROR_CONSTANT } from "#veryfront/errors";
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 · 145 lines · 37 tokens per session scan A 40450492692d
vf-module-development is a skill published in the GitHub repository veryfront/veryfront-code (18 stars, last pushed 2d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,106 once invoked, about $0.0002 per session on Opus 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
rove
Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — rove api send, never a peer/MCP side channel.
general-video
The fallback workflow for authoring custom HyperFrames video compositions at any length or format — longer or multi-scene pieces, brand / sizzle reels, montages, title cards, static loops, and freeform compositions. Input- and length-agnostic. If a specialized workflow clearly fits the input — a marketed product, a…
motion-graphics
Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s…
release
Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, bump/tag/push via scripts/release.sh, then poll the GitHub Actions Release workflow with gh until npm publish completes, diagnosing CI…
file-issue
Turn a rough idea, a bug, or a batch of unsolved problems into well-structured GitHub issue(s) and file them with gh, auto-classifying type + labels from the content (recommend, then confirm) and following Rove's conventions (beginner-friendly framing, concrete file pointers, an acceptance checklist, zero AI/Anthropic…
hyperframes-cli
HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, or remove-background, or when troubleshooting the…