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.
npx agentmods add skills/anastasiyaw/codex-claude-code-config/script-evaluatornpx skills add AnastasiyaW/codex-claude-code-config --skill script-evaluatorgit clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-configWrote 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/skills/anastasiyaw/codex-claude-code-config/script-evaluator)<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/script-evaluator"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/script-evaluator.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 | $0.00155 | $0.01604 |
| Opus 5 | $0.00077 | $0.00802 |
| Sonnet 5 | $0.00031 | $0.00321 |
| Haiku 4.5 | $0.00015 | $0.00160 |
Grade A, and why
script-evaluator 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Script Evaluator / Flatness Detector
Review a video script, presentation, or rendered scene code and identify exactly WHY it's boring and HOW to fix it. Works on scripts, storyboards, and Remotion/code-based video scenes.
Evaluation: 6 Dimensions (score each 1-10)
1. TENSION - Does the viewer feel something?
| Score | Description |
|---|---|
| 1-3 | No enemy/problem. Features listed without context. "We do X, Y, Z" tone |
| 4-6 | Problem mentioned but vague ("saves time"). Some contrast but generic |
| 7-10 | Specific visceral enemy. Clear before→after. Viewer thinks "that's me!" |
Fix: Name the specific pain. Use customer language. Show the "before" state - make it ugly. Add a number to every claim.
2. SPECIFICITY - Is it concrete or vague?
| Red Flag | Fix |
|---|---|
| "Saves time" | HOW MUCH? "Saves 45 minutes per photo" |
| "Better quality" | WHAT metric? "Original DPI, pixel-to-pixel" |
| "Innovative solution" | WHAT innovation? "Neural retouching with layer output" |
| "AI-powered" | What does the AI DO? "Detects and removes 12 types of artifacts" |
| "Trusted by thousands" | WHO? "Used by 500+ jewelry studios including [name]" |
Rule: Replace every adjective with a number or example.
3. EMOTIONAL ARC - Does it go somewhere?
| Score | Description |
|---|---|
| 1-3 | Same energy start to finish. Feels like a slideshow of facts |
| 4-6 | Some variation but no clear peak/valley |
| 7-10 | Identifiable beats. At least one DOWN (tension) and one UP (relief). Last scene feels different from first |
Fix: Map scenes to an emotional curve. Must have at least one DOWN (problem) and one UP (amazement/relief). The CTA should feel like resolution, not another slide.
4. HOOK STRENGTH - Will they keep watching?
| Score | Description |
|---|---|
| 1-3 | Starts with logo, "We are [company]...", or decorative intro with no information |
| 4-6 | Has information but doesn't create urgency or curiosity |
| 7-10 | First frame has surprising information. Creates curiosity gap. Uses customer language. MUST see next scene |
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 · 140 lines · 155 tokens per session scan A 44ab415cbb9e
script-evaluator is a skill published in the GitHub repository AnastasiyaW/codex-claude-code-config (147 stars, last pushed yesterday), licensed MIT. It adds 155 tokens to every session and 1,604 once invoked, about $0.0008 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-30.
Other skills, from other repositories
add-new-model
Add support for a newly-released LLM model in pydantic-ai (e.g. openai:gpt-5.6, anthropic:claude-sonnet-5). Use when a provider ships a new model id and you need to wire literals, profile flags, and tests to recognize it. Handles SDK-lag, gateway list conventions, and capability probing.
building-pydantic-ai-agents
Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydanticai, or asks to build an AI agent, add tools/capabilities, defer capability loading, stream output, define agents…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
testing-skill
Record, rewrite, and debug VCR cassettes for HTTP recordings. Use when running tests with --record-mode, verifying cassette playback, or inspecting request/response bodies in YAML cassettes.
pre-push-review
Run a high-judgment local review of the current branch before pushing, both before a PR exists and between PR iterations.
harness-creator
Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is…