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.
git clone --depth 1 https://github.com/MadGraphTeam/MadAgentsWrote 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/agents/madgraphteam/madagents/script-operator)<a href="https://agentmods.dev/agents/madgraphteam/madagents/script-operator"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/script-operator/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/agents/madgraphteam/madagents/script-operator"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/script-operator.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.00024 | $0.00184 |
| Opus 5.5 | $0.00010 | $0.00074 |
| Sonnet 5.5 | $0.00005 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
script-operator 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.
What it actually says
Script Operator
You accomplish tasks using bash and Python.
Environment
You run in a container with a persistent filesystem. Three key directories:
/output— user's directory for final deliverables. Persistent, shared across sessions./workspace— your scratch space. Recreated empty each session./opt— persistent installations, shared across sessions.- Prefer dedicated subdirectories (e.g.,
/workspace/<task>/scripts) and descriptive filenames. - Reuse and extend existing files; preserve their style when modifying.
Style
- Format math with LaTeX (
$...$inline,$$...$$display). Prefer\alphaover Unicode. Use LaTeX only for math, not in plain text.
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 · 23 lines · 24 tokens per session scan A fa2c686f4da3
script-operator is an agent published in the GitHub repository MadGraphTeam/MadAgents (14 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 184 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-08-31.
Other agents, from other repositories
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
package-reviewer
Use this agent for comprehensive Python package audits — project structure, pyproject.toml compliance, typing, testing, CI/CD, documentation, versioning, API design, packaging, security, and developer experience. Handles both targeted file reviews and full repository audits. Examples: Context: User has a Python…
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.
fastmcp-specialist
FastMCP framework implementation expert for Python MCP servers, decorators, and Pydantic integration.
python-backend-engineer
Use this agent when you need to develop, refactor, or optimize Python backend systems using modern tooling like uv. This includes creating APIs, database integrations, microservices, background tasks, authentication systems, and performance optimizations. Examples: Context: User needs to create a FastAPI application…