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/jared833/claude-code-hooks/written-redraftnpx skills add jared833/claude-code-hooks --skill written-redraftgit clone --depth 1 https://github.com/jared833/claude-code-hooksWrote 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/jared833/claude-code-hooks/written-redraft)<a href="https://agentmods.dev/skills/jared833/claude-code-hooks/written-redraft"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/written-redraft.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.00086 | $0.01115 |
| Opus 5 | $0.00043 | $0.00558 |
| Sonnet 5 | $0.00017 | $0.00223 |
| Haiku 4.5 | $0.00009 | $0.00112 |
Grade A, and why
written-redraft 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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redraft queue for newsletter/blog
Engage's /written page lets Jared leave a note instead of editing text himself. That note gets
written straight to buildlog as status: redraft and a note field, queued rather than acted on
instantly (his call, 2026-08-19: a real rewrite happening the moment he clicks submit needs an
LLM call inside that request, the same per-use API cost as buildlog's disabled Regenerate
button, which he already declined once). This skill is that queue's processor: a real Claude Code
session, run off his existing subscription, not a metered API call.
What this does NOT cover
Drafting the week's content from scratch is /post-week's job. This skill only rewrites entries
already sitting at status: redraft. If nothing is at that status, say so and stop; do not go
looking for other work to do.
Steps
-
Fetch buildlog's origin first.
git -C <HOME>\projects\buildlog fetch origin && git -C <HOME>\projects\buildlog checkout main && git -C <HOME>\projects\buildlog pull --rebase. A stale checkout means rewriting a version of the file that already changed underneath it. -
Find every
status: redraftfile inbuildlog/src/content/newsletters/andbuildlog/src/content/posts/. If there are none, report that and stop, nothing to do. -
Read the standards before rewriting anything, same as
/post-weekdoes at drafting time:buildlog/scripts/voice.mjs- the sales voice (short declarative sentences, concrete numbers, problem then mechanism then result, no em/en dashes).buildlog/docs/content-pillars.md- the seven pillars and the product honesty guardrails. It names which products may be mentioned in a draft, at what price, and which are shelved and must never be named, priced or teased. Keep that list in your own repo.- Newsletters additionally follow the four-section format (Shipped, Broke, Steal this, Worth
knowing) documented in
content-pillars.md's "Newsletter format" section.
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.
- 4d ago First seen · 68 lines · 86 tokens per session scan A 87aa7b0fe444
written-redraft is a skill published in the GitHub repository jared833/claude-code-hooks (2 stars, last pushed 3d ago), licensed MIT. It adds 86 tokens to every session and 1,115 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…