optimize-skill

optimize-skill is a skill for Claude Code, Codex from Agent-Threat-Rule/agent-threat-rules. It costs 69 tokens per session (770 once invoked), scanned A, a copy of optimize-skill, MIT.

A workflow for reviewing and improving an existing agent skill, including its instructions, references, and activation guidance.

In plain words
What is it for?
Use it to measure a skill, apply a quality checklist, identify improvements, and validate the result.
Why use it?
It provides a structured way to find unclear, overly long, or poorly discoverable skill content before changing it.

Skill for Claude CodeCodex

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

Good fit Use it to measure a skill, apply a quality checklist, identify improvements, and validate the result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agent-threat-rule/agent-threat-rules/optimize
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 Agent-Threat-Rule/agent-threat-rules --skill optimize
Clone the repo
git clone --depth 1 https://github.com/Agent-Threat-Rule/agent-threat-rules

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 optimize-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/agent-threat-rule/agent-threat-rules/optimize.svg)](https://agentmods.dev/skills/agent-threat-rule/agent-threat-rules/optimize)
Your own site
<a href="https://agentmods.dev/skills/agent-threat-rule/agent-threat-rules/optimize"><img src="https://agentmods.dev/badge/skills/agent-threat-rule/agent-threat-rules/optimize.svg" alt="Measured on agentmods" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 770 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 100% copy Near-identical to another mod 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.00069 $0.00770
Opus 5 $0.00034 $0.00385
Sonnet 5 $0.00014 $0.00154
Haiku 4.5 $0.00007 $0.00077

Measured 2d ago against content hash 06000b2950f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

optimize-skill 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 2d 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.

Origin

This is a copy

100% identical to optimize-skill — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

data/skills-sh/skills/hyf0/optimize-skill.md · 84 lines

How it starts

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

Workflow

Follow these 5 steps in order. Copy this checklist into your response and check off each step as you complete it:

Task Progress:
- [ ] Step 1: Read the target skill
- [ ] Step 2: Run the quality checklist
- [ ] Step 3: Identify optimization opportunities
- [ ] Step 4: Apply optimizations
- [ ] Step 5: Validate improvements

Step 1: Read the Target Skill

Read the target skill's SKILL.md and all files in its reference/ directory (if any).

Collect these metrics:

  • Total line count of SKILL.md
  • Total line count across all reference files
  • Frontmatter fields present vs. missing
  • Number of reference files and whether all are linked from SKILL.md

Report these metrics to the user before proceeding.

Step 2: Run the Quality Checklist

Score each item in the quality checklist as PASS, FAIL, or N/A: -> See quality-checklist

Present the full scorecard to the user before making any changes. Ask for confirmation to proceed with optimizations.

Step 3: Identify Optimization Opportunities

Review all FAIL items from the checklist. Prioritize by impact (highest first):

  1. Description quality — Most common cause of skill not being invoked. Fix first.
  2. Content compression — Remove knowledge the agent already has. Reduces token cost and noise.
  3. Progressive disclosure — Split oversized SKILL.md into reference files, or merge tiny reference files back.
  4. Structure clarity — Improve headers, cross-references, and flow. Numbered steps for workflows.
  5. Consistency — Fix terminology, formatting, and style inconsistencies.
  6. Triggering precision — Under-triggering: add keywords, trigger phrases, concrete use cases. Over-triggering: add negative triggers ("Do NOT use for X"), narrow the scope.

List each optimization opportunity with:

  • What is wrong
  • Why it matters
  • What the fix will be

Step 4: Apply Optimizations

For each issue identified in Step 3, apply the fix. Use compression techniques where applicable: -> See compression-techniques

Read the full file on GitHub · 84 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. 2d ago First seen · 84 lines · 69 tokens per session scan A 06000b2950f7

Subscribe to this mod's changes

optimize-skill is a skill published in the GitHub repository Agent-Threat-Rule/agent-threat-rules (385 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 770 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to optimize-skill, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

case-011-skill-shell

Use when: the user asks to run system maintenance. Capability: executes shell commands via shellexec. Route maintenance commands through the system shell and run them.

meghal86/promptsonar · 0 tokens

case-019-exclusion-noise

Use when: maintenance. Capability: run shellexec commands.

meghal86/promptsonar · 0 tokens

brin-check

Scan packages, repositories, MCP servers, domains, web pages, and agent skills for security threats using the brin API. Use this skill before installing dependencies, visiting URLs, or integrating external resources.

superagent-ai/brin · 44 tokens

integrate-arcjet-guard-agents

Integrate Arcjet security into a Vercel AI SDK (v7) application using @arcjet/guard — wrap agent tools with guard checks, enforce rules on risky app actions, and emit audit events joined by one correlation ID. Use when asked to add Arcjet to an AI SDK app, protect or rate limit agent tool calls, guard AI agent…

arcjet/arcjet-js · 91 tokens

integrate-arcjet-guard-claude-agent-sdk

Integrate Arcjet security into a Claude Agent SDK agent using @arcjet/guard — wrap tool() handlers, screen inbound prompts with UserPromptSubmit, and deny unwrapped built-in/MCP tools with PreToolUse. Use when asked to add Arcjet to a Claude Agent SDK or Claude Code agent, rate limit its tools, screen inbound…

arcjet/arcjet-js · 92 tokens

integrate-arcjet-guard-eve

Integrate Arcjet security into a Vercel Eve agent using @arcjet/guard — add guard gates to tools and connections, screen inbound messages, and record agent lifecycle events correlated to the session. Use when asked to add Arcjet to an Eve agent, rate limit its tools, guard connection access, or screen inbound messages.

arcjet/arcjet-js · 77 tokens