vrk bare

vrk –bare creates symlinks so you can call any tool by name without the vrk prefix.

The problem

A multicall binary means typing the prefix on every invocation. In an interactive session where you run 30 commands in a row, the prefix is pure friction.

The solution

vrk --bare creates symlinks so you can call any tool by name directly: tok, jwt, epoch instead of vrk tok, vrk jwt, vrk epoch. Symlinks point back to the same binary. Nothing is copied. Remove them with --remove.

Before and after

Before

alias tok='vrk tok'
alias jwt='vrk jwt'
alias epoch='vrk epoch'
# repeat for 28 tools...

After

vrk bare

Example

vrk --bare --dry-run

Exit codes

Flags

How it works

Create symlinks

$ vrk bare
Created 26 symlinks in /usr/local/bin/

Each tool gets a symlink: tok -> vrk, jwt -> vrk, epoch -> vrk, etc. The multicall binary detects which name it was invoked as and dispatches to the right tool.

Preview before creating (–dry-run)

$ vrk bare --dry-run
Would create: /usr/local/bin/tok -> /usr/local/bin/vrk
Would create: /usr/local/bin/jwt -> /usr/local/bin/vrk
Would create: /usr/local/bin/epoch -> /usr/local/bin/vrk
...

Check existing symlinks (–list)

$ vrk bare --list
tok -> /usr/local/bin/vrk
jwt -> /usr/local/bin/vrk
epoch -> /usr/local/bin/vrk

Remove symlinks (–remove)

$ vrk bare --remove
Removed 26 symlinks

Only removes symlinks that point to the vrk binary. Other files with the same names are left untouched.

Overwrite conflicts (–force)

If a file already exists at a symlink path, --force replaces it:

vrk bare --force

Without --force, existing files are skipped with a warning.

After setup

# Before: vrk prefix required
vrk tok --check 8000 < prompt.txt

# After: direct invocation
tok --check 8000 < prompt.txt
grab https://example.com | prompt --system 'Summarize'

All flags and piping work identically.