offense

offense is a skill for Claude Code, Codex from OutlineDriven/odin-claude-plugin. It costs 49 tokens per session (1,270 once invoked), scanned A, original, Apache-2.0.

A workflow for rebuilding a software subsystem from its stated contracts when a human explicitly requests an overhaul. It replaces the old structure and updates the code that depends on it.

In plain words
What is it for?
Rewriting a subsystem from scratch, removing obsolete structures, simplifying special cases, and migrating all callers in one change.
Why use it?
It is intended for cases where incremental patches would preserve a broken design or leave duplicate paths behind.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the odin-code plugin — 60 skills shipped together

Good fit Rewriting a subsystem from scratch, removing obsolete structures, simplifying special cases, and migrating all callers in one change.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/outlinedriven/odin-claude-plugin/offense
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 OutlineDriven/odin-claude-plugin --skill offense
Clone the repo
git clone --depth 1 https://github.com/OutlineDriven/odin-claude-plugin

Made for: Claude Code, Codex.

Or install odin-code, the plugin that ships this one along with the rest of its 60 skills.

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 offense

README.md
[![agentmods](https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/offense/github.svg)](https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/offense)
Your own site
<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/offense"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/offense/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 offense

Your own site · 80×15
<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/offense"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/offense.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,270 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.00049 $0.01270
Opus 5.5 $0.00020 $0.00508
Sonnet 5.5 $0.00010 $0.00254
Haiku 4.5 $0.00005 $0.00127

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

Security

Grade A, and why

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

plugins/odin-code/skills/offense/SKILL.md · 40 lines

How it starts

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

Offense

Radical codebase overhaul, invoked by a human only. Demolish-and-re-derive: rewrite subsystems from their contracts instead of patching, delete rather than deprecate, collapse special cases into the general case, and migrate every caller in the same change. The stance is offensive, tear the broken structure out and re-derive it clean, not defensive patching that leaves the old shape half alive.

Contract

Field Bound contract
Trigger A human invokes an overhaul: "overhaul", "rebuild this subsystem", "rewrite it from scratch", or equivalent. Never self-initiated.
Authority Human-gated: asks before removing any observable surface consumers depend on; otherwise reversible local: writes only the invoked scope (an exact disclosed set of repository paths); rollback is version control (atomic commits). No remote mutation.
Side effect Atomic compilable commits that demolish the old structure and re-derive it from its contracts; the general case absorbs every special case; every caller migrates in the same change; no shim, alias, deprecated path, or feature flag survives the cutover.
Done The invoked scope is rebuilt from its contracts, every caller is migrated, no special-case branch or deprecated path remains, the feature works end to end, and the applicable verifier is green.

Inputs

Supply the invoked scope (the subsystem, module set, or surface to overhaul), the contracts that govern it, and the permitted path set. Supply required verification commands when the repository does not define them. An implementation plan or known invariants are optional; derive them from the existing contracts when absent, but do not invent requirements.

Procedure

  1. Bound the invoked scope. List the exact repository paths in the overhaul and the observable surfaces it exposes (public APIs, CLI flags, config keys, file formats, wire shapes). Stop and ask before removing any observable surface consumers depend on; never silently narrow scope. Done when: the exact path set and observable surfaces are listed, and removal of any consumer-facing surface is explicitly approved.
  2. Re-derive the contract. Read the existing implementation and extract the contract the subsystem should have held: its invariants, trust boundaries, and the general case that absorbs every special case. Discard the old structure's accidents; keep only the contract. Done when: the contract is written with invariants, trust boundaries, and the general case named.
  3. Partition into atomic increments. Each increment must preserve the named invariants, compile, and leave applicable existing behavior verifiable. Order increments so the contract is re-derived before callers migrate onto it. Done when: the work is partitioned into increments that each compile and preserve invariants.
  4. Demolish and re-derive. Implement the general case directly from the contract. Encode invariants in types or construction where practical; otherwise validate at the boundary and return or raise the repository's explicit error form. Delete the old structure rather than deprecating it; collapse every special-case branch into the general rule; do not leave a shim, alias, deprecated path, or feature flag for the old shape. Done when: the general case is implemented, the old structure is deleted, and no special-case branch, shim, alias, or dark flag remains.
  5. Migrate every caller in the same change. Update every callsite to the new contract in the same change that introduces it; never leave a caller on a removed surface. If a caller cannot migrate within the disclosed path set, stop and ask: do not widen scope implicitly and do not leave a half-migrated state. Done when: every caller is migrated and no reference to a removed surface remains.
  6. Verify each increment. After each increment, run the narrowest applicable compile and behavioral checks that exercise its changed contract. If they pass, commit that one logical change with a descriptive message. Revalidate all named invariants affected by the next increment before continuing. Done when: each increment is checked, committed, and its invariants revalidated for the next increment.
  7. Exercise end to end and run the final verifier. Confirm the changed-path set is exactly the disclosed set, that no special-case branch, shim, alias, deprecated path, or uncommitted partial increment remains, and that the feature works end to end. Done when: end-to-end behavior is exercised, the final verifier is green, and the changed-path set matches the disclosed set with no remnants.

Read the full file on GitHub · 40 lines

Files

What ships with it

1 file 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. 1mo ago Changed · -40 tokens per session 6010c278b662
  2. 1mo ago First seen · 40 lines · 89 tokens per session scan A 2d3e8acd13cc

Subscribe to this mod's changes

offense is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (37 stars, last pushed 21d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,270 once invoked, about $0.0002 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-09-04.

Related

Other skills, from other repositories

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

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens