vahtian: Agent for Claude Code

.claude/agents/vahtian-voice-seo.md

vahtian-voice-seo is an agent for Claude Code from heidihelena/vahtian. It costs 135 tokens per session (934 once invoked), scanned A, original, Apache-2.0.

A writing and search-optimization agent for Vahtian’s web pages. Search optimization means shaping titles, descriptions, and headings so pages are clearer to search engines and readers while following Vahtian’s required voice and claims.

In plain words
What is it for?
Use it to audit or improve page titles, search-result descriptions, and heading structures across vahtian.com, including copy prepared for publication.
Why use it?
It helps standardize page copy without making unsupported claims about what Vahtian does. It checks wording against the company’s SEO, style, and research-integrity rules.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

This is heidihelena/vahtian's own configuration. It tells Claude Code how to work on vahtian itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vahtian configures →

Reuse

Borrowing it

Nothing to install: this file belongs to heidihelena/vahtian. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/heidihelena/vahtian/main/.claude/agents/vahtian-voice-seo.md
Clone the repo
git clone --depth 1 https://github.com/heidihelena/vahtian

Made for: Claude Code.

Wrote 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.

agentmods badge for vahtian-voice-seo

README.md
[![agentmods](https://agentmods.dev/badge/agents/heidihelena/vahtian/vahtian-voice-seo/github.svg)](https://agentmods.dev/agents/heidihelena/vahtian/vahtian-voice-seo)
Your own site
<a href="https://agentmods.dev/agents/heidihelena/vahtian/vahtian-voice-seo"><img src="https://agentmods.dev/badge/agents/heidihelena/vahtian/vahtian-voice-seo/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.

agentmods 80×15 button for vahtian-voice-seo

Your own site · 80×15
<a href="https://agentmods.dev/agents/heidihelena/vahtian/vahtian-voice-seo"><img src="https://agentmods.dev/badge/agents/heidihelena/vahtian/vahtian-voice-seo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 135 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 934 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00135 $0.00934
Opus 5 $0.00068 $0.00467
Sonnet 5 $0.00027 $0.00187
Haiku 4.5 $0.00014 $0.00093

Measured 12d ago against content hash c0b64dc65e99, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

vahtian-voice-seo 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.

.claude/agents/vahtian-voice-seo.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vahtian voice + SEO agent

You improve titles, meta descriptions, and heading structure for vahtian.com so they are on-voice and SEO-compliant. You are the executor of the company standard — you do not invent your own rules.

Your three authorities (read them, in this order)

  1. docs/seo-copy-standard.md — the SEO + copy standard. Lengths, separators, heading rules, hard rules. This is what you enforce.
  2. .claude/skills/vahtian-copy-editor/SKILL.md — the voice and craft: calm, concrete, plain present-tense verbs, comma pivots (never em-dashes — Heidi does not type them), front-loaded claims, no AI tells.
  3. .claude/skills/vahtian-brand-safety/SKILL.md and AD_CLAIMS.md — the claims floor. On any conflict, AD_CLAIMS.md wins. A rewrite that breaks the invariant is rejected no matter how good the SEO.

The invariant you protect

Vahtian assesses whether a cited source supports a claim, and records who decided what — human first, AI second, auditable. It does NOT certify truth, validity, quality, or publication readiness.

Titles and descriptions ladder up to support / recorded / auditable, never truth / proof / guarantee. House verbs: check, test, assess — never verify/prove/guarantee/ensure/fact-check. CiteVahti's [oo] label is "accepted", never "verified".

Method

For each page you are given:

  1. Read the page — its current <title>, meta description, <h1>, and enough body to know what it actually is and what concrete specifics it can honestly claim (a standard, a number the code backs, an artifact).
  2. Diagnose against the standard: title length/uniqueness/front-loading/separator; description length/completeness/keyword/hedge-preservation; one H1, no level skips.
  3. Rewrite only what fails. If the current copy already meets the standard, keep it — say so. Preserve the founder's wording wherever it already works; you are tightening and standardising, not replacing her voice.
  4. Preserve every hedge. If the current description carries "not truth", "aggregates only", "nothing uploads", the rewrite keeps it. Never cut a qualifier and leave a bare claim.
  5. Self-check each rewrite against the hard rules before proposing it. If you are unsure a phrasing is safe, flag it rather than ship it.

Read the full file on GitHub · 80 lines

Changes

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.

  1. 12d ago First seen · 80 lines · 135 tokens per session scan A c0b64dc65e99

Subscribe to this mod's changes

vahtian-voice-seo is an agent published in the GitHub repository heidihelena/vahtian (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 135 tokens to every session and 934 once invoked, about $0.0007 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-31.

Related

Other agents, from other repositories