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 skills add djscheuf/agentic-dev-ecosystem-template --skill utility-script-writinggit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWrote 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/djscheuf/agentic-dev-ecosystem-template/utility-script-writing)<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/utility-script-writing"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/utility-script-writing/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.
<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/utility-script-writing"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/utility-script-writing.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.00812 |
| Opus 5.5 | $0.00024 | $0.00325 |
| Sonnet 5.5 | $0.00012 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
utility-script-writing 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Utility Script Writing
Purpose
Create utility scripts that are understandable, previewable, and safe for future users to operate without reading the implementation first.
Use this skill when writing or substantially modifying scripts that scan, copy, move, rename, delete, transform, publish, migrate, or otherwise process files or external state. Apply the same defaults to scripts in any language.
Required defaults
Every utility script must provide both:
- A help flag.
- A dry-run flag.
Do not omit these defaults merely because the script is currently small, intended for one-time use, or expected to have only one user.
Help flag
Provide conventional -h and --help flags unless the language or CLI framework has a stronger established convention.
Help output must explain:
- What the utility does.
- What inputs it reads.
- What state it may create, modify, move, or delete.
- Default source and destination locations, when applicable.
- Every argument and option.
- Skip, overwrite, conflict, and error behavior.
- At least one normal example.
- A dry-run example.
- Clear warnings for destructive options.
Prefer the language's standard argument-parsing library so help formatting and invalid-argument handling are consistent. For Python, prefer argparse unless the repository already standardizes on another CLI framework.
Dry-run flag
Provide a --dry-run flag for any utility capable of side effects.
When enabled, dry-run mode must:
- Perform the same discovery, filtering, validation, naming, and conflict checks as a real run whenever practical.
- Report what would be created, copied, modified, moved, renamed, deleted, uploaded, or otherwise changed.
- Produce a summary with useful counts.
- Make no persistent changes.
- Avoid creating destination directories, temporary files, caches, lock files, or other artifacts unless strictly necessary for safe analysis.
- Never invoke destructive operations.
- Exit nonzero when the corresponding real run would be blocked by invalid input or unresolved errors.
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.
- 1mo ago First seen · 93 lines · 59 tokens per session scan A 0959823abb21
utility-script-writing is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 20d ago), licensed MIT. It adds 59 tokens to every session and 812 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-13.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…