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 queelius/claude-anvil --skill prose-craftgit clone --depth 1 https://github.com/queelius/claude-anvilWrote 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/queelius/claude-anvil/prose-craft)<a href="https://agentmods.dev/skills/queelius/claude-anvil/prose-craft"><img src="https://agentmods.dev/badge/skills/queelius/claude-anvil/prose-craft/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/queelius/claude-anvil/prose-craft"><img src="https://agentmods.dev/badge/skills/queelius/claude-anvil/prose-craft.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00079 | $0.02067 |
| Opus 5.5 | $0.00032 | $0.00827 |
| Sonnet 5.5 | $0.00016 | $0.00413 |
| Haiku 4.5 | $0.00008 | $0.00207 |
Grade A, and why
prose-craft 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 yesterday.
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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fiction Prose Craft
Practical guardrails for writing fiction. Each rule is a thing that goes wrong in drafts, especially AI-assisted drafts, and how to fix it.
Prose Craft
Show, don't name the sensation. "Her hands were shaking" not "she felt afraid." The reader should infer the emotion from the physical detail. When you name the emotion directly, you shortcut the reader's experience of it. The physical detail makes them feel it; the label just tells them about it.
Before: She felt a surge of grief. After: She opened the cabinet and his coffee mug was still there, handle turned out the way he always left it.
Concrete and sensory. Name the object, the sound, the texture. "The fluorescent light buzzed" not "the room felt sterile." Abstraction is the default mode of lazy prose. Every time you reach for an adjective like "eerie" or "beautiful," ask what specific sensory detail would make the reader reach that conclusion on their own.
Vary sentence rhythm. Short sentences for impact, longer for texture. Three short sentences in a row creates urgency. A long sentence after them releases it. Read the paragraph aloud: if it drones, the rhythm is flat. This isn't a rule about sentence length. It's a rule about pacing.
The door opened. He stepped in. The room was empty. She'd taken everything: the books, the lamp, the framed photograph from their trip to the coast that he'd always assumed meant as much to her as it did to him.
No purple prose, no cliches. "Her eyes were pools of liquid sapphire" is not prose, it's decoration. Precision matters as much here as in technical writing: it's just applied to different material. If a phrase sounds like you've read it a hundred times before, you have, and so has the reader.
Cut adverbs that duplicate the verb. "She whispered quietly": the verb already did that work. "He sprinted quickly": what else would sprinting be? Adverbs earn their place only when they contradict or modify: "she whispered fiercely" does real work because it creates tension between the quietness of whispering and the intensity of the delivery.
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.
- yesterday Changed · -8 lines 95b4f5e39d44
- 4d ago First seen · 176 lines · 79 tokens per session scan A 1b7a30b9f0f2
prose-craft is a skill published in the GitHub repository queelius/claude-anvil (2 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 2,067 once invoked, about $0.0003 per session on Opus 5.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-10-19.
Other skills, from other repositories
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
karpenter
Design, install, debug, review, plan capacity, audit scaling history, migrate from Cluster Autoscaler, and upgrade Karpenter v1.x on EKS. Covers NodePool, EC2NodeClass, NodeClaim, Spot diversity, disruption strategy, Pod Identity/IRSA, interruption queue, private clusters, AMI rotation, and GitOps integration. Use…
azure
Azure identity (Workload Identity, OIDC, Entra ID), resource tagging, AKS platform patterns, RBAC scoping, and production-readiness review — with Terraform generation.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
kubescape
Check Kubernetes manifests, Helm charts, Kustomize overlays and live clusters against NSA-CISA, MITRE ATT&CK, CIS (EKS, AKS, GKE, vanilla) and SOC2 with the Kubescape CLI. Covers framework choice, score and severity gates, PR gates that fail only on new findings (--baseline), exceptions that actually suppress…