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 Rezenders/scientific_writing_agent --skill write-to-intentgit clone --depth 1 https://github.com/Rezenders/scientific_writing_agentWrote 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/rezenders/scientific_writing_agent/write-to-intent)<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>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.00052 | $0.01394 |
| Opus 5 | $0.00026 | $0.00697 |
| Sonnet 5 | $0.00010 | $0.00279 |
| Haiku 4.5 | $0.00005 | $0.00139 |
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.
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:
- Goal: what should this passage establish, argue, or introduce? (one or two sentences is enough)
- Target: file and line range (existing passage to rewrite, or insertion point for new text)
- Context: the preceding and following paragraph(s) — paste text or give file:line
- 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.
- What is the rhetorical function of this passage? (e.g., motivate, define, bridge, summarize, introduce)
- Who is the implied reader at this point in the paper? (expert in the subfield? broad audience?)
- Are there specific terms, concepts, or examples from the manuscript that must appear?
- Are there any claims this passage must NOT make (to avoid overstating or conflicting with elsewhere)?
- 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
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.
- 8d ago First seen · 161 lines · 52 tokens per session scan A bcf956697332
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.
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…
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…
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…
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…
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…