Borrowing it
Nothing to install: this file belongs to owenob1/prompt-improver. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/owenob1/prompt-improver/main/CLAUDE.mdgit clone --depth 1 https://github.com/owenob1/prompt-improverWrote 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.
[](https://agentmods.dev/instructions/owenob1/prompt-improver/claude-md)<a href="https://agentmods.dev/instructions/owenob1/prompt-improver/claude-md"><img src="https://agentmods.dev/badge/instructions/owenob1/prompt-improver/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.01791 | $0.01791 |
| Opus 5 | $0.00896 | $0.00896 |
| Sonnet 5 | $0.00358 | $0.00358 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade A, and why
prompt-improver CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this is
A pure-Bash Agent Skill (no build step, no package manager, no compiled code). It takes a vague coding request and rewrites it into a structured XML spec by shelling out to a separate coding CLI (claude, grok, codex, gemini, …) headlessly, then hands the result back to the host agent to execute.
Commands
bash tests/smoke-test.sh # full suite — this is what CI runs
bash skills/prompt-improver/scripts/smoke-test.sh # skill-package checks only (14 groups, faster)
There is no test-name filter. To iterate on one check, run the underlying script directly:
cd skills/prompt-improver
bash scripts/validate-prompt.sh examples/fixtures/valid-prompt.xml # expect exit 0
bash scripts/validate-prompt.sh examples/fixtures/invalid-prompt.xml # expect exit 1
bash scripts/assemble-generation-prompt.sh "some request" # inspect assembled generator prompt
bash scripts/gather-context.sh . # inspect deterministic context block
bash scripts/generate-prompt.sh --raw-input "..." --mode plan --skip-validate # end-to-end, needs a CLI on PATH
Group [1/8] of the skill smoke test runs bash -n over every scripts/**/*.sh, so syntax errors are caught without a separate lint step. There is no typecheck, formatter, or linter.
Architecture
Host agent session (Claude Code / Grok / …)
└─ scripts/generate-prompt.sh orchestrator
├─ lib/settings.sh settings + model/backend resolution + limit detection
├─ gather-context.sh deterministic repo facts (shell only, never AI search)
├─ assemble-generation-prompt.sh references + context + raw request → one prompt file
├─ backends/<cli>.sh headless invoke of the generator CLI
└─ validate-prompt.sh structural checks on the XML
└─ host executes the XML (execute mode) or shows it (plan mode)
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.
- 7d ago First seen · 90 lines · 1,791 tokens per session scan A a115b35f70b3
prompt-improver CLAUDE.md is an instructions file published in the GitHub repository owenob1/prompt-improver (6 stars, last pushed 1mo ago), licensed MIT. It adds 1,791 tokens to every session, about $0.0090 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-08-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.