agentmods.dev

rewrite-for-audience

rewrite-for-audience is a skill for Claude Code, Codex from jezweb/vite-flare-starter. It costs 48 tokens per session (551 once invoked), scanned A, original, MIT.

A writing skill for adapting existing text to a different audience, tone, length, or format while preserving its meaning. It first identifies what facts and messages must remain unchanged.

In plain words
What is it for?
Use it to simplify text, rephrase it, formalize it, shorten or expand it, or convert it into formats such as emails, summaries, scripts, or social posts.
Why use it?
It helps turn the same source material into clearer, more formal, simpler, shorter, or audience-specific writing without losing important details.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 48repo 17d ago A scan SkillSpector: pass 48 tokens original MIT

Good fit Use it to simplify text, rephrase it, formalize it, shorten or expand it, or convert it into formats such as emails, summaries, scripts, or social posts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jezweb/vite-flare-starter/rewrite-for-audience
View source ↗ jezweb/vite-flare-starter
Install

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.

Any agent
npx skills add jezweb/vite-flare-starter --skill rewrite-for-audience
Clone the repo
git clone --depth 1 https://github.com/jezweb/vite-flare-starter

Made for: Claude Code, Codex.

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 rewrite-for-audience

README.md
[![agentmods](https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/rewrite-for-audience/github.svg)](https://agentmods.dev/skills/jezweb/vite-flare-starter/rewrite-for-audience)
Your own site
<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/rewrite-for-audience"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/rewrite-for-audience/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 rewrite-for-audience

Your own site · 80×15
<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/rewrite-for-audience"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/rewrite-for-audience.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 551 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00048 $0.00551
Opus 5 $0.00024 $0.00275
Sonnet 5 $0.00010 $0.00110
Haiku 4.5 $0.00005 $0.00055

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

Security

Grade A, and why

rewrite-for-audience 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.

skills/rewrite-for-audience/SKILL.md · 54 lines

How it starts

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

Rewrite for Audience

When to use

The user has source text and wants it adapted. Examples:

  • "Rewrite this for a non-technical audience"
  • "Make this more formal"
  • "Simplify this paragraph"
  • "Turn these notes into a press release"
  • "Rewrite for LinkedIn"

Steps

  1. Identify the rewrite parameters — if not specified, ask via ask_questions:

    • Audience (technical experts, general public, executives, customers, students)
    • Tone (formal, conversational, persuasive, neutral, urgent)
    • Format (email, blog post, social media, summary, script)
    • Length (shorter, longer, same)

  2. Read the source carefully — identify:

    • Core message (what must survive the rewrite)
    • Specific facts/numbers (must remain accurate)
    • Voice/perspective (first/second/third person)

  3. Rewrite — apply transformations:

    • Simpler language: replace jargon with plain terms; shorter sentences
    • More formal: avoid contractions, use precise vocabulary, third person
    • More casual: contractions OK, conversational rhythm, second person
    • For executives: lead with the conclusion/ask, support with brief evidence
    • For social media: hook in first line, scannable, one idea
    • For non-experts: define jargon, use analogies, examples first

  4. Preserve facts — never change numbers, names, dates, or specific claims.

  5. Show comparison if useful — use show_comparison to display original vs rewritten side-by-side.

  6. Offer iterations — use offer_choices: "Make it shorter", "More technical", "Different tone", "Looks good".

Style notes

  • For Australian audiences: Australian English spelling, no Americanisms
  • Match the source's structure unless format is being changed
  • Don't add information that wasn't in the source
  • Keep the same point of view unless the rewrite calls for change

What not to do

  • Don't dumb down to the point of inaccuracy
  • Don't add jargon to make it "sound smarter"
  • Don't change the meaning — adapt how it's said, not what's said
  • Don't pad to hit a length target — be concise

Read the full file on GitHub · 54 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 · 54 lines · 48 tokens per session scan A b3bb3c2a18f0

Subscribe to this mod's changes

rewrite-for-audience is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 17d ago), licensed MIT. It adds 48 tokens to every session and 551 once invoked, about $0.0002 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.

Writing and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens