A prompt-refinement guide activated only by the explicit /better or $better command. It asks for deeper methods, source material, tools, and ways to check the result before rewriting the task.

It is for improving prompts or strengthening an already-running task when the user explicitly requests that mode.

It helps turn a shallow task request into a more specific brief without simply making it longer.

How OpenAgentsInc/openagents configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to OpenAgentsInc/openagents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/OpenAgentsInc/openagents/main/.agents/skills/better/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/OpenAgentsInc/openagents

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/openagentsinc/openagents/better/github.svg)](https://agentmods.dev/skills/openagentsinc/openagents/better)

Your own site

<a href="https://agentmods.dev/skills/openagentsinc/openagents/better"><img src="https://agentmods.dev/badge/skills/openagentsinc/openagents/better/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/openagentsinc/openagents/better"><img src="https://agentmods.dev/badge/skills/openagentsinc/openagents/better.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 414 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.00414
Opus 5.5	$0.00014	$0.00166
Sonnet 5.5	$0.00007	$0.00083
Haiku 4.5	$0.00003	$0.00041

Measured 4d ago against content hash 72bae97a7f43, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

better 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 4d 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

Copies of this mod

1 near-identical copy found in the catalogue:

better — 100% identical, 0 lines differ

.agents/skills/better/SKILL.md · 20 lines

What it actually says

I want a deeper version of this task, not a bigger one. Before rewriting it: (1) say what a top professional in this field would do here that I'm not asking for; (2) name the rawest material they would start from instead of what has already been digested for me; (3) name the specific methods and tools they would use; (4) say what, other than you or me, would show the result is right. Then rewrite my prompt to ask for exactly that.

How to apply it

First decide which case you are in.

Case A: the user gave you a prompt to improve. The text with the command is a prompt or task they have not started yet. Give your answers to (1) to (4), then the rewritten prompt. Do not carry the prompt out.

Case B: work is already in progress. The command came alone, or with feedback on work you have already done in this conversation ("not good enough", "too shallow"). "This task" is that work, and the feedback is part of the task.

Give your answers to (1) to (4) for that task, in a few lines each.
Rewrite the task's brief: the original request plus the user's feedback, deepened by your answers.
Decide whether to pause. If the new brief changes the goal, widens the scope, or needs a decision, money or access that only the user can give, show it and wait for their go-ahead. Otherwise carry on.
Do the work again to the new brief. Start from the raw material in your answer to (2), use the methods and tools in your answer to (3), and before you report, run the check in your answer to (4) and say what it showed.

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.

4d ago First seen · 20 lines · 34 tokens per session scan A 72bae97a7f43

Subscribe to this mod's changes

better is a skill published in the GitHub repository OpenAgentsInc/openagents (458 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 414 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-20.

Planning

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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 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

openagents: Skill for Claude Code