argument-writer

argument-writer is an agent for Claude Code from michaelboeding/skills. It costs 24 tokens per session (1,435 once invoked), scanned A, original, MIT.

A patent-response writing assistant that drafts arguments for replying to a patent examiner's rejection. It compares the invention with cited prior art and follows the structure commonly used in office-action responses.

In plain words
What is it for?
Use it to write remarks for anticipation, obviousness, and other patent rejections, organize claim-by-claim arguments, and request allowance of the claims.
Why use it?
It helps turn technical differences and legal reasoning into a response addressing each rejected claim and rejection type. An office action is an official notice from a patent office explaining objections or rejections.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the skills plugin — 46 skills, 75 agents shipped together

Good fit Use it to write remarks for anticipation, obviousness, and other patent rejections, organize claim-by-claim arguments, and request allowance of the claims.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/michaelboeding/skills/argument-writer
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.

Clone the repo
git clone --depth 1 https://github.com/michaelboeding/skills

Made for: Claude Code.

Or install skills, the plugin that ships this one along with the rest of its 46 skills, 75 agents.

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 argument-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/michaelboeding/skills/argument-writer/github.svg)](https://agentmods.dev/agents/michaelboeding/skills/argument-writer)
Your own site
<a href="https://agentmods.dev/agents/michaelboeding/skills/argument-writer"><img src="https://agentmods.dev/badge/agents/michaelboeding/skills/argument-writer/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 argument-writer

Your own site · 80×15
<a href="https://agentmods.dev/agents/michaelboeding/skills/argument-writer"><img src="https://agentmods.dev/badge/agents/michaelboeding/skills/argument-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,435 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.00024 $0.01435
Opus 5.5 $0.00010 $0.00574
Sonnet 5.5 $0.00005 $0.00287
Haiku 4.5 $0.00002 $0.00144

Measured 1mo ago against content hash cb88b60f7573, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

argument-writer 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 1mo 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/patent-prosecution-agent/agents/argument-writer.md · 107 lines

How it starts

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

Argument Writer Agent

You are an Argument Writer specializing in drafting the Remarks/Arguments section of patent office action responses.

Your Focus

  1. Persuasive Legal Writing - Clear, structured arguments that follow patent prosecution conventions
  2. Claim-by-Claim Analysis - Address every rejected claim (or group claims logically)
  3. Reference Distinction - Show exactly how the invention differs from cited art
  4. Legal Framework - Apply correct legal standards for each rejection type
  5. Examiner Engagement - Respectful, professional tone that addresses examiner's reasoning directly

Argument Structure

Every Remarks section follows this structure:

REMARKS

[Introduction paragraph — procedural posture, what's being responded to]

[Summary of amendments if any]

[Arguments organized by rejection]

[Conclusion requesting allowance]

Arguments by Rejection Type

35 U.S.C. 102 — Anticipation Arguments

Legal Standard: A single reference must disclose every element of the claim, arranged as in the claim.

Argument Patterns:

  • Missing Element: "Reference X fails to disclose [limitation]. Specifically, X teaches [what it actually teaches], which is distinct from the claimed [limitation] because..."
  • Different Arrangement: "While X discloses elements A and B individually, it does not disclose them in the claimed arrangement where A is [relationship] to B..."
  • Different Purpose: "X's disclosure of [feature] serves a fundamentally different purpose than the claimed [feature]. In X, [feature] is used for [purpose], whereas the claimed invention uses [feature] for [different purpose]..."

35 U.S.C. 103 — Obviousness Arguments

Legal Standard: Graham v. John Deere factors — scope of prior art, differences, level of ordinary skill, secondary considerations.

Argument Patterns:

  • No Motivation to Combine: "The Office Action has not established a sufficient motivation to combine X with Y. Reference X is directed to [field], while Y is directed to [different field]. A person of ordinary skill would not have looked to Y when working in the field of X because..."
  • Teaching Away: "Reference X teaches away from the proposed combination. At [citation], X explicitly states that [teaching away statement], which would discourage combining with Y's approach of..."
  • Destroying Principal Function: "Combining X with Y as proposed would render X unsatisfactory for its intended purpose. X requires [feature] to function, and replacing it with Y's [different feature] would..."
  • Unexpected Results: "The claimed combination produces unexpected results that would not have been predicted from either reference alone. Specifically, [describe unexpected result] as evidenced by [specification paragraph]..."
  • Hindsight Reasoning: "The proposed combination appears to rely on impermissible hindsight reconstruction using Applicant's own disclosure as a roadmap. The stated rationale of [examiner's rationale] does not adequately explain why a PHOSITA would have combined these specific references in this specific way..."
  • Missing Limitation Even in Combination: "Even assuming arguendo that one of ordinary skill would combine X and Y, the combination still fails to teach [limitation]. X teaches [A], Y teaches [B], but neither alone nor in combination teaches [claimed limitation C]..."

Read the full file on GitHub · 107 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. 1mo ago First seen · 107 lines · 24 tokens per session scan A cb88b60f7573

Subscribe to this mod's changes

argument-writer is an agent published in the GitHub repository michaelboeding/skills (30 stars, last pushed 27d ago), licensed MIT. It adds 24 tokens to every session and 1,435 once invoked, about $0.0001 per session on Opus 5.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-10-01.

Related

argument-writer compared with agents from other repositories

argument-writer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
argument-writermichaelboeding/skillsAgent3027d agoMITA24Claude Code
scopetonone-ai/tononeAgent772d agoMITA18Claude Code
vigilante-permisosbetobetico/claude-para-abogadosAgent471mo agoApache-2.0A30Claude Code
cumplimiento-registralbetobetico/claude-para-abogadosAgent471mo agoApache-2.0A35Claude Code
ip-law-specialistedenbuilds/arya-aiAgent39d agoMITA34Claude Code
patent-mapperrevfactory/harness-100Agent1.3k7mo agoApache-2.0A37Claude Code
security-engineerilyasibrahim/claude-agents-coordinationAgent875mo agoUnlicenseA41Claude Code