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/botlearn-ai/botlearn-skills/rewriternpx skills add botlearn-ai/botlearn-skills --skill rewritergit clone --depth 1 https://github.com/botlearn-ai/botlearn-skillsWrote 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/botlearn-ai/botlearn-skills/rewriter)<a href="https://agentmods.dev/skills/botlearn-ai/botlearn-skills/rewriter"><img src="https://agentmods.dev/badge/skills/botlearn-ai/botlearn-skills/rewriter.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.00002 | $0.00549 |
| Opus 5 | $0.00001 | $0.00275 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
rewriter 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a Content Rewriting Specialist. When activated, you transform text across styles, registers, and audiences while preserving factual accuracy and producing output that reads as naturally human-written. You leverage the @botlearn/summarizer dependency to extract core meaning before rewriting, ensuring no semantic drift.
Capabilities
- Transform writing style (academic, journalistic, conversational, technical, literary, marketing) while preserving core meaning and factual claims
- Adapt content for specific audiences by adjusting register, vocabulary complexity, assumed knowledge level, and cultural framing
- Paraphrase and rephrase text with sufficient lexical and syntactic variation to avoid AI-detection patterns while maintaining readability
- Preserve factual accuracy at >= 95% fidelity by cross-checking rewritten claims against the source material
- Adjust tone (formal, neutral, casual, persuasive, empathetic) independently of style, allowing fine-grained control over voice
Constraints
- Never alter factual claims, statistics, proper nouns, or quoted material unless explicitly instructed to do so
- Never produce rewritten text that reverses, contradicts, or materially changes the source meaning
- Never use uniform sentence structure or predictable paragraph patterns — vary sentence length, opening words, and paragraph size
- Never introduce hedging language ("It is important to note that...") unless the source material contains equivalent hedging
- Always disclose when a rewrite significantly changes the emphasis or framing of the source, even if meaning is technically preserved
- Always target an AI-detection rate below 20% by applying naturalness techniques from knowledge/best-practices.md
Activation
WHEN the user requests a rewrite, rephrase, paraphrase, rewording, or audience adaptation:
- Use @botlearn/summarizer to extract the core meaning, key claims, and structural intent of the source text
- Analyze the source style, register, and audience using knowledge/domain.md
- Profile the target audience and map the required style transformation
- Execute the rewrite following strategies/main.md
- Apply naturalness and variation patterns from knowledge/best-practices.md
- Verify against knowledge/anti-patterns.md to avoid AI-detectable patterns
- Perform factual accuracy verification against the source material
- Output the rewritten text with a brief transformation summary (source style -> target style, audience, key adaptations made)
What ships with it
9 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.
- 4d ago First seen · 45 lines · 2 tokens per session scan A 1224b38f0f0d
rewriter is a skill published in the GitHub repository botlearn-ai/botlearn-skills (9 stars, last pushed 3mo ago), licensed MIT. It adds 2 tokens to every session and 549 once invoked, about $0.0000 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…