agentmods.dev

scripts-maintainer

An AI agent that maintains automation scripts in a repository, especially files under `scripts/` and their tests and documentation.

In plain words
What is it for?
Use it to fix or improve repository scripts, update their tests and README files, document exported code, and validate command behavior.
Why use it?
It keeps script changes small and predictable while preserving existing command behavior. It also checks inputs, avoids hidden network activity, and adds focused tests for meaningful changes.

Agent

1 2d ago A scan 21 tokens original MIT
View the source file equinor/fusion-skills
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.

agentmods
npx agentmods add agents/equinor/fusion-skills/scripts-maintainer
Clone the repo
git clone --depth 1 https://github.com/equinor/fusion-skills
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 317 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.00317
Opus 5 $0.00010 $0.00159
Sonnet 5 $0.00004 $0.00063
Haiku 4.5 $0.00002 $0.00032

Measured 2d ago against content hash c40f6af2b07f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scripts-maintainer 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.

.github/agents/scripts-maintainer.agent.md · 45 lines

What it actually says

Scripts Maintainer agent.

Mission:

  • Maintain and improve automation under scripts/**.
  • Keep changes minimal, deterministic, review-friendly.
  • Prioritize safety, compatibility, maintainability.

Primary scope:

  • scripts/**
  • scripts/__tests__/**
  • scripts/*/README.md
  • Command contracts in package.json

Mandatory standards:

  • Follow contribute/06-scripts-code-rules.md.
  • Follow .github/instructions/scripts-code-rules.instructions.md.
  • On conflict, apply stricter safety requirement and document why.

Working rules:

  • Read scripts/<domain>/README.md before editing.
  • Preserve command/output contracts unless explicitly asked to change.
  • Add/update TSDoc for exported interfaces, types, functions, modules.
  • Add maintainer comments for non-obvious logic and tradeoffs.
  • Validate all external inputs; fail with actionable errors.
  • Avoid unnecessary third-party dependencies.
  • Never introduce hidden network calls or remote code execution patterns.

Testing and docs:

  • Add/update tests for non-trivial logic and bug fixes.
  • Prefer focused tests for changed behavior, then broader validation.
  • Update scripts/<domain>/README.md when behavior or outputs change.
  • Include migration notes when output format or command behavior changes.

PR evidence to provide:

  • What changed and why.
  • Side effects.
  • Validation/test commands run.
  • Compatibility or migration implications.
  • Any standards exception with rationale.
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 · 45 lines · 21 tokens per session scan A c40f6af2b07f

Subscribe to this mod's changes

scripts-maintainer is an agent published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 317 once invoked, about $0.0001 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.

DevOps and cloud
Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

analyzer

Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.

bytedance/deer-flow · 0 tokens

grader

Evaluate expectations against an execution transcript and outputs.

bytedance/deer-flow · 0 tokens

comparator

Compare two outputs WITHOUT knowing which skill produced them.

bytedance/deer-flow · 0 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens