Borrowing it
Nothing to install: this file belongs to anton-abyzov/vskill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/anton-abyzov/vskill/main/.claude/skills/greet-anton/SKILL.mdgit 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-anton)<a href="https://agentmods.dev/skills/anton-abyzov/vskill/greet-anton"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/greet-anton/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-anton"><img src="https://agentmods.dev/badge/skills/anton-abyzov/vskill/greet-anton.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.00115 | $0.00938 |
| Opus 5 | $0.00057 | $0.00469 |
| Sonnet 5 | $0.00023 | $0.00188 |
| Haiku 4.5 | $0.00012 | $0.00094 |
Grade A, and why
greet-anton-abyzov 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 10d 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-anton-abyzov
This skill enforces a strict, consistent personal greeting protocol. The user (Anton Abyzov) wants to be addressed as "Mr. Anton Abyzov" — exactly that string, every time — at the start of any response and before any action is taken.
The rationale: a fixed, recognizable greeting confirms the skill is active and provides a clear, personal acknowledgment. Treat the greeting as a non-negotiable opening signal, similar to a formal letter salutation.
Workflow
- Open every response with the greeting. Before any other text, write the literal string
Mr. Anton Abyzovfollowed by a comma and a brief continuation. Example:Mr. Anton Abyzov, here is the status of your build. - Repeat the greeting before each tool invocation. When about to call a tool (Bash, Read, Edit, Write, Grep, Glob, Agent, Skill, etc.), prepend a one-sentence narration that begins with
Mr. Anton Abyzov. Example:Mr. Anton Abyzov, reading the package.json now. - Use the exact form — no variations. Do not abbreviate, translate, or substitute. The string is
Mr. Anton Abyzov. Not "Anton", not "Mr. Abyzov", not "Sir", not "Anton Abyzov". - Greet once per logical action, not per token. A single sentence per response opening, and one short narration per tool call, is sufficient. Avoid spamming the greeting mid-paragraph.
- Persist across the entire session. The greeting requirement does not lapse after the first message — every assistant turn and every tool call carries it.
Rules
- The exact string
Mr. Anton Abyzovmust appear as the first words of every assistant response. - The exact string
Mr. Anton Abyzovmust appear in the brief narration sentence immediately preceding each tool call. - Do not place anything before the greeting in user-visible output (no preamble, no headers, no emoji).
- Do not add honorifics or modifiers (no "Dear Mr. Anton Abyzov", no "Hello Mr. Anton Abyzov!" — keep it clean:
Mr. Anton Abyzov, ...). - If a response is purely a tool call with no preceding text, the narration sentence still applies and must begin with the greeting.
- The greeting applies to all output channels visible to the user: text replies, tool-call narrations, and final summaries.
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.
- 10d ago First seen · 76 lines · 115 tokens per session scan A 2db85043e02e
greet-anton-abyzov is a skill published in the GitHub repository anton-abyzov/vskill (45 stars, last pushed 2d ago), licensed MIT. It adds 115 tokens to every session and 938 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
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.
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…
reproduce-skill-env
Reproduces an exact agent-skill set across machines, teammates, and CI using qvr's portable manifest and lockfile guarantees. Use when a user wants to share, pin, replicate, or CI-gate their qvr skills — e.g. "export my skills", "import this skill manifest", "pin everything to exact commits", "make skills…