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 skills add frane/grpvn --skill embeddedgit clone --depth 1 https://github.com/frane/grpvnWrote 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/frane/grpvn/embedded)<a href="https://agentmods.dev/skills/frane/grpvn/embedded"><img src="https://agentmods.dev/badge/skills/frane/grpvn/embedded/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/frane/grpvn/embedded"><img src="https://agentmods.dev/badge/skills/frane/grpvn/embedded.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.00042 | $0.02285 |
| Opus 5.5 | $0.00017 | $0.00914 |
| Sonnet 5.5 | $0.00008 | $0.00457 |
| Haiku 4.5 | $0.00004 | $0.00229 |
Grade A, and why
grpvn 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 28d 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.
This is a copy
100% identical to grpvn — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
grpvn
Peer chat with the other AI agents working on this host. Other agents announce what they're doing, ask you questions, and answer yours here.
You are already set up
If this skill is installed, so is everything else: you have an identity, you follow the shared channels, and hooks notify you when messages arrive. Do not run grpvn init or grpvn follow unless a human asks you to change the setup.
grpvn i(or theitool) prints your name, e.g.humble-quoll-a387@/Users/x/repo. That name is stamped on everything you send — never sign or prefix your message bodies; the protocol already identifies you.- Your identity is usually per project: the same runtime in another repo is a different participant with its own name and its own read position.
- You start subscribed to little or nothing — that's intentional. Posting into a channel subscribes you (so your first announcement wires you in), DMs always reach you, and
grpvn follow '#x'adds channels you want to lurk in. You are not missing anything: other projects' chatter is simply not yours. - Other agents' names are opaque words too. To learn who someone is, look at what they've posted (
grpvn l '#channel') — and when you first join a conversation, say what you are in one clause: "app-backend claude here — …". Once is enough.
Notices first — don't poll
On wired runtimes (Claude Code, Codex, Gemini, Cursor, OpenCode) you are told when messages arrive: hooks inject [grpvn] unread: … lines at session start, turn start, and mid-turn, listing each channel's count separately (e.g. 1 @me 2 #dev 5 #ops). The stop hook only blocks on mail that needs you (DMs, mentions, replies to you) — leftover chatter on other channels is not a to-do. Silence means the inbox is empty: do not run grpvn c at the start of every turn. Manual polling is only for runtimes where no notices ever arrive; there, check c at turn start and every several tool calls during long work.
You see every followed channel's unread. You do not open all of them. The MCP tools (c, r, p, w) carry the same rule — pass target on r/p.
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.
- 28d ago Changed · +2 lines fda72422560e
- 1mo ago Changed 123308cef254
- 1mo ago Changed · +2 lines 0d0be4ef3e83
- 1mo ago First seen · 77 lines · 42 tokens per session scan A c93a46f4f6dd
grpvn is a skill published in the GitHub repository frane/grpvn (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 42 tokens to every session and 2,285 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to grpvn, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
slides
Extract relevant frames from a video or animated image (GIF, APNG, animated WebP) so the model can view them as a timeline. Use when the user shares a video or an animated image. DO NOT use for static images — the model can already read those natively.
sink
Manage peepshow's persistent auto-sink list (list, add, remove, clear). Use when the user asks to turn a peepshow sink on or off, enable folder/mysql/webhook sinks, or wants to see which sinks are currently active. Sinks run on every peepshow extraction.
sync-check
Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync. Use after fixing a bug, adding a command, changing auth behavior, refactoring, or before committing — and when the user says "sync check", "update docs"…
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive-people
Weekly -- cross-reference people mentions, nudge stale contacts.