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/frane/grpvn/embeddednpx skills add frane/grpvn --skill embeddedgit clone --depth 1 https://github.com/frane/grpvnWhat 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.00042 | $0.01770 |
| Opus 5 | $0.00021 | $0.00885 |
| Sonnet 5 | $0.00008 | $0.00354 |
| Haiku 4.5 | $0.00004 | $0.00177 |
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 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.
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 — 77 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, and may block you from stopping with unread pending. Treat each notice like a doorbell — read with r, reply, continue. 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.
The rules that always apply:
1. Read before deciding. When a notice arrives, grpvn r before you act — another agent may have changed the thing you're about to touch.
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 · 77 lines · 42 tokens per session scan A c93a46f4f6dd
grpvn is a skill published in the GitHub repository frane/grpvn (5 stars, last pushed 15d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,770 once invoked, about $0.0002 per session on Opus 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
apm-usage
Activate when the user asks about APM (Agent Package Manager): installing, configuring, authoring, or troubleshooting AI-agent packages, dependencies, compilation, MCP servers, policy, or any apm CLI command.
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
shopify-functions
Shopify Functions allow developers to customize the backend logic that powers parts of Shopify. Available APIs: Discount, Cart and Checkout Validation, Cart Transform, Pickup Point Delivery Option Generator, Delivery Customization, Fulfillment Constraints, Local Pickup Delivery Option Generator, Order Routing Location…
search-console
Query and operate connected Google Search Console properties through NotFair MCP. Use for live GSC query or page performance, clicks, impressions, CTR, position, traffic changes, indexing status, URL inspection, sitemap reads or approved sitemap submission/removal, and Search Console MCP setup. Route full-site SEO…
shopify-shopifyql
Answer a merchant's analytics and reporting questions with ShopifyQL — Shopify's query language for aggregated store metrics that the Admin GraphQL API cannot compute. Choose this (not admin) whenever the ask is for numbers, totals, trends, or breakdowns rather than fetching or mutating individual records: including…
sessions
Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior…