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/hamsurang/kit/velog-clinpx skills add hamsurang/kit --skill velog-cligit clone --depth 1 https://github.com/hamsurang/kitWhat 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.00114 | $0.01407 |
| Opus 5 | $0.00057 | $0.00704 |
| Sonnet 5 | $0.00023 | $0.00281 |
| Haiku 4.5 | $0.00011 | $0.00141 |
Grade A, and why
velog-cli 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
velog-cli Skill
velog is a CLI client for velog.io, a developer blogging platform.
It lets you manage blog posts entirely from the terminal — create from markdown files,
edit, publish drafts, browse trending posts, and more.
Prerequisites
The velog binary must be installed:
# macOS
brew tap hamsurang/velog-cli && brew install velog-cli
# Cargo (any platform)
cargo install velog-cli
If velog is not found, tell the user to install it first.
Authentication
Most write operations require authentication. Check status before attempting mutations.
# Check if logged in
velog auth status
# Login (interactive — prompts for tokens from browser DevTools)
velog auth login
# Logout
velog auth logout
How to get tokens: The user opens velog.io in their browser, opens DevTools (F12) →
Application → Cookies, and copies access_token and refresh_token. The CLI prompts
for these during velog auth login.
Credentials are stored at ~/.config/velog-cli/credentials.json and auto-refresh when expired.
Post Management
List Posts
# List your own posts (requires auth)
velog post list
# List your drafts
velog post list --drafts
# Trending posts (filterable by period)
velog post list --trending
velog post list --trending --period week
# Recent posts across velog
velog post list --recent
# Posts by a specific user
velog post list -u <username>
# Control result count (1–100, default 20)
velog post list --limit 50
# Pagination
velog post list --recent --cursor <cursor>
velog post list --trending --offset 20
Show a Post
# Show your own post by slug
velog post show <slug>
# Show another user's post
velog post show <slug> -u <username>
The slug is the URL path segment (e.g., my-first-post from velog.io/@user/my-first-post).
Create a Post
# From a markdown file (saved as draft by default)
velog post create -t "Post Title" -f article.md
# From stdin
echo "# Hello World" | velog post create -t "Hello"
# Publish immediately (not draft)
velog post create -t "Title" -f article.md --publish
# With tags and custom slug
velog post create -t "Title" -f article.md --tags "rust,cli,velog" --slug my-custom-slug
# Private post
velog post create -t "Title" -f article.md --publish --private
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 · 208 lines · 114 tokens per session scan A 555fe4dd432e
velog-cli is a skill published in the GitHub repository hamsurang/kit (19 stars, last pushed 4mo ago), licensed MIT. It adds 114 tokens to every session and 1,407 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…