anti-defensive-writing

anti-defensive-writing is a skill for Claude Code, Codex from Boom5426/Nature-Paper-Skills. It costs 201 tokens per session (2,069 once invoked), scanned A, original, MIT.

A writing editor that removes unnecessary hedges, disclaimers, apologies, and defensive explanations while keeping limits needed for accuracy, safety, law, or method.

In plain words
What is it for?
Use it to revise papers, reports, or other drafts whose claims are buried under excessive caveats.
Why use it?
It makes a draft more direct without deleting important qualifications.

Skill for Claude CodeCodex

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

Good fit Use it to revise papers, reports, or other drafts whose claims are buried under excessive caveats.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/boom5426/nature-paper-skills/anti-defensive-writing
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 Boom5426/Nature-Paper-Skills --skill anti-defensive-writing
Clone the repo
git clone --depth 1 https://github.com/Boom5426/Nature-Paper-Skills

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 anti-defensive-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/anti-defensive-writing/github.svg)](https://agentmods.dev/skills/boom5426/nature-paper-skills/anti-defensive-writing)
Your own site
<a href="https://agentmods.dev/skills/boom5426/nature-paper-skills/anti-defensive-writing"><img src="https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/anti-defensive-writing/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 anti-defensive-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/boom5426/nature-paper-skills/anti-defensive-writing"><img src="https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/anti-defensive-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 201 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,069 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.00201 $0.02069
Opus 5 $0.00101 $0.01035
Sonnet 5 $0.00040 $0.00414
Haiku 4.5 $0.00020 $0.00207

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

Security

Grade A, and why

anti-defensive-writing 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 7d 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/core/anti-defensive-writing/SKILL.md · 262 lines

How it starts

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

Anti-Defensive Writing

Run this at the rhetorical-posture layer, not first. See Local integration at the end of this file for where it sits in the paper-workflow chain and which limitations it must never delete.

Core Rule

Advance the claim directly.

Say what is true, what the text argues, what the evidence shows, or what the method does. Do not default to explaining what the text does not claim, does not prove, does not imply, does not cover, or does not attempt.

Use a calm, competent authorial posture. Write as an author explaining an argument to the reader, not as an author negotiating with an imagined critic.

Preserve Necessary Precision

Keep limitations when they are necessary for accuracy, ethics, law, safety, or methodological transparency.

A limitation is necessary when it affects:

  • the validity of the claim;
  • the interpretation of the evidence;
  • the scope of application;
  • the research design;
  • the reader's ability to use the result correctly.

Write necessary limitations once, clearly and calmly. Place them in the appropriate section, usually methods, discussion, or limitations. Do not scatter them through abstracts, introductions, contribution paragraphs, topic sentences, conclusions, or executive summaries unless the limitation is essential to that exact sentence.

Detection Checklist

Before finalizing a draft or revision, check for:

  • unnecessary disclaimers;
  • repeated statements of what the text does not claim;
  • excessive hedging;
  • caveats in high-impact positions;
  • paragraphs that start with limitations;
  • negative framing where positive framing would work;
  • explanations added only to prevent hypothetical misunderstanding;
  • self-undermining contribution statements;
  • unnecessary "not X but Y" structures;
  • redundant "however", "nevertheless", or "although" transitions.

Revise any item that weakens the text without improving accuracy.

Rewrite Procedure

  1. Identify the function of the defensive sentence.

Classify it as one of:

Read the full file on GitHub · 262 lines

Files

What ships with it

2 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.

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. 7d ago First seen · 262 lines · 201 tokens per session scan A 7557e433d223

Subscribe to this mod's changes

anti-defensive-writing is a skill published in the GitHub repository Boom5426/Nature-Paper-Skills (490 stars, last pushed 7d ago), licensed MIT. It adds 201 tokens to every session and 2,069 once invoked, about $0.0010 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-09-05.

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