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/ibm-self-serve-assets/building-blocks/maximo-code-optimizationnpx skills add ibm-self-serve-assets/building-blocks --skill maximo-code-optimizationgit clone --depth 1 https://github.com/ibm-self-serve-assets/building-blocksWrote 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/ibm-self-serve-assets/building-blocks/maximo-code-optimization)<a href="https://agentmods.dev/skills/ibm-self-serve-assets/building-blocks/maximo-code-optimization"><img src="https://agentmods.dev/badge/skills/ibm-self-serve-assets/building-blocks/maximo-code-optimization.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.00043 | $0.04685 |
| Opus 5 | $0.00022 | $0.02343 |
| Sonnet 5 | $0.00009 | $0.00937 |
| Haiku 4.5 | $0.00004 | $0.00468 |
Grade A, and why
maximo-script-optimizer 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 3d 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 — 645 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maximo Automation Script Optimizer
Metadata
- Name: Maximo Automation Script Optimizer
- Version: 1.0.0
- Description: Expert skill for analyzing, optimizing, and securing IBM Maximo automation scripts with comprehensive best practices
- Author: Maximo Development Team
- Tags: maximo, automation-scripts, jython, python, optimization, security, performance
Overview
This skill transforms Bob into an expert Maximo automation script optimizer with deep knowledge of:
- Maximo automation scripting best practices
- Security vulnerability detection and remediation
- Performance optimization techniques
- Resource management and memory leak prevention
- Error handling and logging strategies
- Maximo API usage patterns
- Script testing and validation
When to Use This Skill
Activate this skill when:
- User asks to "optimize my Maximo scripts" or "optimize the scripts"
- Fetching automation scripts from a Maximo environment
- Analyzing existing Maximo automation scripts for issues
- Optimizing script performance and resource usage
- Identifying and fixing security vulnerabilities (SQL injection, etc.)
- Adding proper error handling and logging
- Reviewing scripts before production deployment
- Troubleshooting script-related production issues
- Creating new automation scripts following best practices
- Conducting code reviews for Maximo scripts
Interactive Workflow
When a user asks to "optimize my Maximo scripts" or "optimize the scripts", follow this systematic workflow:
Phase 1: Environment Setup
- Create Project Structure:
- Create
maximo-scripts/directory in the workspace - Create
maximo-scripts/tools/subdirectory - Copy the fetch script from skill to project:
- Source:
.bob/skills/maximo-code-optimization/tools/fetch_maximo_scripts.py - Destination:
maximo-scripts/tools/fetch_maximo_scripts.py
- Source:
- Create
maximo-scripts/tools/requirements.txtwith dependencies:requests>=2.31.0 python-dotenv>=1.0.0 urllib3>=2.0.0
- Create
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/optimization-example.md 11 KB
- knowledge/core/maximo-scripting-fundamentals.md 9.1 KB
- knowledge/core/performance-optimization.md 14 KB
- knowledge/core/security-best-practices.md 12 KB
- knowledge/INDEX.md 11 KB
- knowledge/procedures/script-optimization-workflow.md 13 KB
- knowledge/reference/quick-reference.md 11 KB
- knowledge/troubleshooting/common-issues.md 14 KB
- tools/fetch_maximo_scripts.py 5.8 KB runs code
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.
- 3d ago First seen · 645 lines · 43 tokens per session scan A c93a94df26e9
maximo-script-optimizer is a skill published in the GitHub repository ibm-self-serve-assets/building-blocks (24 stars, last pushed 9d ago), licensed Apache-2.0. It adds 43 tokens to every session and 4,685 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…