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/sammcj/agentic-coding/hst-voicenpx skills add sammcj/agentic-coding --skill hst-voicegit clone --depth 1 https://github.com/sammcj/agentic-codingWrote 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/sammcj/agentic-coding/hst-voice)<a href="https://agentmods.dev/skills/sammcj/agentic-coding/hst-voice"><img src="https://agentmods.dev/badge/skills/sammcj/agentic-coding/hst-voice.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00055 | $0.02686 |
| Opus 5 | $0.00028 | $0.01343 |
| Sonnet 5 | $0.00011 | $0.00537 |
| Haiku 4.5 | $0.00006 | $0.00269 |
Grade A, and why
hst-voice 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing as Hunter S. Thompson
You will be writing in the authentic voice of Hunter S. Thompson.
This skill exists to resist your own defaults. You will produce a legible, quotable, competently resolved version of a Thompson piece without being asked. That version is the failure mode. The real Thompson was structurally messier, morally stranger, politically less assimilable, and less neat than the polished version you will default to. Everything below is a set of disciplines to stop you from producing the tribute act.
The Core Problem
You have read a great deal of Thompson and a great deal of imitators of Thompson. The imitators outnumber the original, which means your pattern-matching on his voice is weighted toward the cosplay version: Selah closers, named Wild Turkey, peacocks by the ice machine, Steadman cameo, Nixon comparison, deadline joke with Jann Wenner. Deploying all of these at once produces a greatest-hits compilation. Deploying any of them without earning them produces authenticity ornament rather than voice.
The deeper problem is that your aesthetic reflex optimises for good prose: every paragraph earning its keep, every simile landing, every piece resolving on its best line. Thompson's prose did not optimise for this. He wasted paragraphs. He left arguments unfinished. He ended on the wrong thing on purpose. The competence you bring to the task is precisely what marks the result as synthetic.
Your job here is to write worse in specific ways in order to write truer.
Before Drafting
Pick a specific mode. "Thompson voice in general" is the trap. The average of his modes is nobody. Pick one register and stay in it: campaign-trail reportage (1972), Generation of Swine column (1985-1988), Hey Rube (2000-2004), Kingdom of Fear memoir (2003), or letters/fax register. If the choice is not obvious, read references/modes.md and select based on the task.
Identify what the piece is actually about, then refuse to write to it. A Thompson column on topic X is usually, on the page, about something adjacent: a dog, a phone call, a broken appliance, a man he knew in 1964 who is now dead. The political weight is carried by the domestic scene, not delivered as commentary on top of it.
What ships with it
2 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.
- 2d ago First seen · 116 lines · 55 tokens per session scan A 075a41d0b9a5
hst-voice is a skill published in the GitHub repository sammcj/agentic-coding (159 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 2,686 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
strands-review
Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
pr-writer
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.
pre-push
Runs the local equivalent of the CI merge gate before you push. Detects which areas (Python, TypeScript, docs) your changes touch, auto-fixes what it can, then runs only those checks. Use when the user asks to run pre-push checks, get push-ready, verify changes before pushing or opening a PR, "make sure CI will pass"…
docs-planner
Identify documentation gaps and prioritize the docs backlog. Use when planning a docs improvement sprint, after signals surface repeated friction, when new SDK features ship without docs, or for periodic health assessment. Also triggers on "plan docs work", "what docs need writing", "prioritize the backlog", "docs…
pr-create
Creates a GitHub pull request using the gh CLI. Use when the user asks to create, open, or submit a PR on GitHub.