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 kalyvask/winning-writing --skill voice-updategit clone --depth 1 https://github.com/kalyvask/winning-writingWrote 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/kalyvask/winning-writing/voice-update)<a href="https://agentmods.dev/skills/kalyvask/winning-writing/voice-update"><img src="https://agentmods.dev/badge/skills/kalyvask/winning-writing/voice-update/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/kalyvask/winning-writing/voice-update"><img src="https://agentmods.dev/badge/skills/kalyvask/winning-writing/voice-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 77 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 93 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00169 | $0.03182 |
| Opus 5 | $0.00084 | $0.01591 |
| Sonnet 5 | $0.00034 | $0.00636 |
| Haiku 4.5 | $0.00017 | $0.00318 |
Grade A, and why
voice-update 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 9d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Voice update
Source of truth: context/voice-and-style.md and context/about-me.md. This skill is the only writer to those files; every update flows through it.
What this skill does
Three sources behind one skill. Each source pulls voice / identity information from a different upstream, but all flow into the same downstream (proposed diffs to the two context files):
| Source | Reads | Use when |
|---|---|---|
| manual | One dictated rule, paragraph, or fact from the user | User just noticed something about their voice and wants to capture it now |
| memory | Claude Code auto-memory dir (~/.claude/projects/<slug>/memory/) |
Periodic batch pull — what has Claude learned about my style across recent sessions? |
| sent-mail | Last 20-50 sent Gmail messages via the connected Gmail MCP | Audit voice files against ground truth — how do you actually write vs how you claim to |
--source is required. There is no default — the three sources have different scopes and contracts, and picking automatically would hide the trade-off.
How to invoke
/voice-update --source manual "save this rule: I never use 'leverage' as a verb"
/voice-update --source memory
/voice-update --source sent-mail
/voice-update --source sent-mail last 2 weeks
Universal rules (apply to all three sources)
These rules govern every voice-update operation, regardless of source.
Routing
| If the input is about... | Update this file | Section |
|---|---|---|
| A word the user uses | voice-and-style.md |
Words I like |
| A word the user doesn't use | voice-and-style.md |
Banned words |
| A sentence rhythm or structure | voice-and-style.md |
Sentence structure |
| An AI tell to flag | voice-and-style.md |
AI tells |
| A sample paragraph the user likes | voice-and-style.md |
Sample paragraphs |
| A target length or format | voice-and-style.md |
Length targets / Format preferences |
| A posture / register preference | voice-and-style.md |
Posture |
| New job, project, paper, credential | about-me.md |
Trajectory / Public output |
| Where they live, lived, hobbies, languages | about-me.md |
Identity / How I think |
| A specific belief, thesis, or focus | about-me.md |
Primary focus / Public output |
| What Claude should know about them | about-me.md |
What you (Claude) should know |
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.
- 9d ago First seen · 235 lines · 169 tokens per session scan A 2d3ab6e1e569
voice-update is a skill published in the GitHub repository kalyvask/winning-writing (13 stars, last pushed 4d ago), licensed MIT. It adds 169 tokens to every session and 3,182 once invoked, about $0.0008 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
project-memory
Generate a project-specific context file from a brief so an AI assistant remembers your editorial constraints, voice, audience, and quality bar across sessions.
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
claude-md-updater
Scans the session for lessons and workflows, then proposes scoped CLAUDE.md edits. Use for save this lesson or add to context.
context-anchoring
Manage per-feature living documents that capture decisions, constraints, and reasoning across AI sessions during active development. Scoped to feature-level work — design, implementation, bugfix, refactor — not for codebase-wide assessments or product-wide specifications (those define their own document lifecycles).…