write-to-intent

write-to-intent is a skill for Claude Code from Rezenders/scientific_writing_agent. It costs 52 tokens per session (1,394 once invoked), scanned A, original, Apache-2.0.

A workflow for creating or substantially rewriting a manuscript passage to achieve a stated purpose, such as introducing an argument or framing a result. It produces several proposed versions without changing the file until you approve one.

In plain words
What is it for?
Use it for a new paragraph, subsection introduction, or major rewrite when you can provide the goal, location, and surrounding context.
Why use it?
It helps when the problem is what a passage should accomplish, not just its grammar or wording. The stated goal guides the rewrite.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it for a new paragraph, subsection introduction, or major rewrite when you can provide the goal, location, and surrounding context.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rezenders/scientific_writing_agent/write-to-intent
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 Rezenders/scientific_writing_agent --skill write-to-intent
Clone the repo
git clone --depth 1 https://github.com/Rezenders/scientific_writing_agent

Made for: Claude Code.

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 write-to-intent

README.md
[![agentmods](https://agentmods.dev/badge/skills/rezenders/scientific_writing_agent/write-to-intent.svg)](https://agentmods.dev/skills/rezenders/scientific_writing_agent/write-to-intent)
Your own site
<a href="https://agentmods.dev/skills/rezenders/scientific_writing_agent/write-to-intent"><img src="https://agentmods.dev/badge/skills/rezenders/scientific_writing_agent/write-to-intent.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,394 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.
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.00052 $0.01394
Opus 5 $0.00026 $0.00697
Sonnet 5 $0.00010 $0.00279
Haiku 4.5 $0.00005 $0.00139

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

Security

Grade A, and why

write-to-intent 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 8d 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.

.claude/skills/write-to-intent/SKILL.md · 161 lines

How it starts

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

Write to Intent

Overview

Multi-agent pipeline that turns a writing goal ("I want this paragraph to establish X") into 2-3 refined manuscript proposals — without touching the file until the user explicitly approves.

Differs from /technical-paragraph-rewrite (which checks accuracy and fixes an existing paragraph) and /address-reviewer-comment (which responds to a specific critique). This skill starts from what you want the paragraph to do.

When to Use

  • You want a new paragraph or subsection intro with a specific framing
  • You want to substantially rewrite an existing paragraph toward a new rhetorical goal
  • You have rough notes or a sketch and want manuscript-ready prose
  • You want to explore several ways of making the same argument

Not for: minor wording fixes, responding to a reviewer, or accuracy-checking an existing paragraph.


Inputs Required

Provide:

  1. Goal: what should this passage establish, argue, or introduce? (one or two sentences is enough)
  2. Target: file and line range (existing passage to rewrite, or insertion point for new text)
  3. Context: the preceding and following paragraph(s) — paste text or give file:line
  4. Constraints (optional): terminology to preserve, claims to avoid, mandatory content

Phase 0 — Clarifying Questions

Claude asks the user the following before any agent runs. Do not skip.

  1. What is the rhetorical function of this passage? (e.g., motivate, define, bridge, summarize, introduce)
  2. Who is the implied reader at this point in the paper? (expert in the subfield? broad audience?)
  3. Are there specific terms, concepts, or examples from the manuscript that must appear?
  4. Are there any claims this passage must NOT make (to avoid overstating or conflicting with elsewhere)?
  5. Does the passage introduce new technical claims? (if yes, Phase 1a — implementation check — may be needed)

Wait for the user's answers before proceeding.


Phase 1a — Optional: Implementation Check

Read the full file on GitHub · 161 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. 8d ago First seen · 161 lines · 52 tokens per session scan A bcf956697332

Subscribe to this mod's changes

write-to-intent is a skill published in the GitHub repository Rezenders/scientific_writing_agent (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,394 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-08-30.

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

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…

microsoft/vscode · 72 tokens