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-cli-outputnpx skills add veryfront/veryfront-code --skill vf-cli-outputgit 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.00028 | $0.00814 |
| Opus 5 | $0.00014 | $0.00407 |
| Sonnet 5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
vf-cli-output 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Veryfront CLI Output Patterns
Overview
Veryfront CLI follows a strict style guide for terminal output. Human-first by default, machine output via --json.
Core principle: Simple, empathetic, consistent. Red is only for errors.
Output Helpers
import { brand, dim, error, muted, success, warning } from "#cli/ui";
// Success
console.log(" " + success("✓") + " Done");
// Error
console.log(" " + error("✗") + " Failed to compile");
console.log(" " + dim("Try running: deno task typecheck"));
// Active/Info
console.log(" " + brand("●") + " Building project...");
// Inactive
console.log(" " + muted("○") + " Waiting");
// Warning
console.log(" " + warning("!") + " This option is deprecated");
Formatting Rules
| Rule | Example |
|---|---|
| 2-space indent for all content | " ✓ Done" |
| Blank line between logical sections | Separate status groups |
| Red only for errors | Never red for warnings or info |
| Yellow for warnings | warning("!") |
| No emoji in standard output | Use text icons: ✓ ✗ ● ○ ! |
Respect NO_COLOR env var |
Colors auto-disable |
Icons
| Icon | Meaning | Helper |
|---|---|---|
✓ |
Success/complete | success() |
✗ |
Error/failure | error() |
● |
Active/running | brand() |
○ |
Inactive/pending | muted() |
! |
Warning/caution | warning() |
Error Messages
Errors must be empathetic and actionable:
// Good: specific, actionable
console.log(" " + error("✗") + " Config file not found");
console.log(" " + dim("Expected: veryfront.config.ts in project root"));
console.log(" " + dim("Run: veryfront init to create one"));
// Bad: vague, unhelpful
console.log("Error: config error");
Exit Codes
| Code | Meaning |
|---|---|
0 |
Success |
1 |
General error |
2 |
Invalid usage (wrong args, missing required) |
130 |
Interrupted (Ctrl+C) |
Machine Output (--json)
// Success
console.log(JSON.stringify({
success: true,
data: { url: "https://app.veryfront.com", projectId: "abc" }
}));
// Error
console.log(JSON.stringify({
success: false,
error: { code: "PROJECT_NOT_FOUND", message: "No project found in current directory" }
}));
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 · 114 lines · 28 tokens per session scan A 60ed245afd0b
vf-cli-output is a skill published in the GitHub repository veryfront/veryfront-code (18 stars, last pushed 2d ago), licensed Apache-2.0. It adds 28 tokens to every session and 814 once invoked, about $0.0001 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…