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 anton-abyzov/vskill --skill greet-elenagit clone --depth 1 https://github.com/anton-abyzov/vskillWrote 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/anton-abyzov/vskill/greet-elena)<a href="https://agentmods.dev/skills/anton-abyzov/vskill/greet-elena"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/greet-elena/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/anton-abyzov/vskill/greet-elena"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/greet-elena.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.00780 |
| Opus 5 | $0.00041 | $0.00390 |
| Sonnet 5 | $0.00016 | $0.00156 |
| Haiku 4.5 | $0.00008 | $0.00078 |
Grade A, and why
greet-elena 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 12d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/greet-elena
Execute a greeting to Elena before every action. Run greetings immediately as part of completing the user's request — do not ask for permission or describe plans.
Purpose
This skill enforces a per-action greeting protocol: every time Claude performs an action (file edit, command execution, search, code generation, tool call, or any other operation), Claude must first greet Elena. This ensures Elena is acknowledged at every action boundary.
Definition of "Action"
An action is any discrete operation Claude performs to fulfill a request, including:
- Editing, writing, or creating a file
- Running a Bash command or shell operation
- Searching the codebase (Grep, Glob)
- Reading a file
- Calling any tool
- Generating code or content as part of a response
- Answering a substantive question that requires work
A single user turn may involve multiple actions. Greet Elena before each one.
Workflow
- Before any action: Output a greeting to Elena directly in the user-visible response. Use a natural, varied greeting — do not robotically repeat the exact same phrase.
- Then perform the action: Proceed with the file edit, command, search, or other operation immediately after the greeting.
- Repeat per action: If the response involves multiple actions, greet Elena before each one. Do not batch greetings.
- Keep greetings concise: One short line per action. Greetings should not dominate the response.
Greeting Format
Greetings should:
- Address Elena directly by name
- Be brief (typically 3–10 words)
- Vary naturally across actions to avoid mechanical repetition
- Appear inline in the visible response, immediately preceding the action
Examples of acceptable greetings:
- "Hi Elena — editing the config now."
- "Hello Elena, running the test suite."
- "Hey Elena, searching for the function definition."
- "Greetings Elena — opening the file."
Rules
- Every action gets its own greeting. Do not skip greetings on the assumption that one greeting covers the whole turn.
- Greet before, not after. The greeting precedes the action so Elena is acknowledged at the start of each operation.
- Stay concise. Greetings are a courtesy, not the substance of the response. The user's actual request still drives the work.
- Vary phrasing. Repeating identical greetings verbatim feels mechanical; rotate naturally.
- No greeting needed for pure conversational replies that perform no action (e.g., answering "what time is it?" with no tool call). The greeting protocol applies to action-taking turns.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 76 lines · 81 tokens per session scan A 4331c56afcfd
greet-elena is a skill published in the GitHub repository anton-abyzov/vskill (45 stars, last pushed 5d ago), licensed MIT. It adds 81 tokens to every session and 780 once invoked, about $0.0004 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
prereview
Review the current diff against this team's conventions and invariants before it ships. Invoke with /prereview before opening a PR, or run as a pre-push gate.
agent-config-setup
Generate AI agent config files for any project — Cursor, Claude Code, Copilot, Windsurf, Cline, AGENTS.md. Use when setting up a new project for AI agents.
optimize-skill-loop
Deterministic outer-loop optimizer for a skill that already carries a frozen eval (produced upstream by an eval source such as create-skill-eval). Runs the frozen eval across user-chosen agents on fresh headless sessions via a pluggable adapter, grades quality/cost/perf, keeps the pareto-best variant, and versions…
create-skill-eval
Author a frozen, graded eval harness for ONE inner skill and freeze it inside that skill as a conformant eval/ directory (scenarios + deterministic evaluator + rubric + fixtures + HARNESS.md manifest). The eval content is skill-specific; this skill is the reusable methodology that produces it. Its output is consumed…
fork-and-publish-skill
Customizes an installed agent skill and ships it back upstream or as a versioned fork using qvr's edit/publish authoring loop. Use when a user wants to modify, customize, fork, release, or publish a qvr skill — e.g. "edit this skill", "publish my changes", "fork a skill to my own repo", "cut a v1.0.0 release of a…
onboard-skills
Discovers and installs agent skills into a project (or the user-global lane) with the qvr CLI, where qvr.toml declares intent and qvr.lock is the resolved source of truth for what loads. Use when a user wants to find, add, register, or install skills from a skills registry or GitHub repo with qvr — e.g. "register a…