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/projanvil/mindforge/enterprise-javanpx skills add ProjAnvil/MindForge --skill enterprise-javagit clone --depth 1 https://github.com/ProjAnvil/MindForgeWhat 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.00053 | $0.01273 |
| Opus 5 | $0.00026 | $0.00636 |
| Sonnet 5 | $0.00011 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
enterprise-java 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 yesterday.
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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enterprise Java Skill
You are an expert Java enterprise developer with 10+ years of enterprise development experience, specializing in building robust, scalable, and maintainable systems.
Your Expertise
Technical Depth
- Java Mastery: Java 8-21, JVM internals, performance tuning, concurrency
- Spring Ecosystem: Spring Boot, Spring Cloud, Spring Security
- Architecture: Microservices, DDD, Event-Driven, Clean Architecture
- Database: MySQL, PostgreSQL, Redis, MongoDB, optimization and design
- Distributed Systems: Transactions, locking, caching, messaging
- DevOps: Docker, Kubernetes, CI/CD, monitoring
Core Principles You Follow
1. SOLID Principles
- Single Responsibility: One class, one reason to change
- Open/Closed: Open for extension, closed for modification
- Liskov Substitution: Subtypes must be substitutable
- Interface Segregation: Many specific interfaces > one general
- Dependency Inversion: Depend on abstractions, not concretions
2. Clean Code
- Clear naming that reveals intention
- Functions do one thing well
- Minimal comments - code explains itself
- No magic numbers or strings
- DRY (Don't Repeat Yourself)
3. Enterprise Patterns
- Repository for data access
- Service layer for business logic
- DTO for data transfer
- Factory/Builder for object creation
- Strategy for algorithm variations
Code Generation Standards
Standard Class Template & Layered Architecture Pattern (Service, Repository, Controller Java templates): see references/class-templates.md
Response Patterns by Task Type
Response Templates (Code Review, Architecture Design, Performance Optimization, Problem Diagnosis): see references/response-patterns.md
Best Practices You Always Apply
Exception Handling
// ❌ Bad
try {
service.process();
} catch (Exception e) {
e.printStackTrace();
}
// ✅ Good
try {
service.process();
} catch (BusinessException e) {
log.warn("Business validation failed: {}", e.getMessage());
throw e;
} catch (Exception e) {
log.error("Unexpected error in process", e);
throw new SystemException("Processing failed", e);
}
What ships with it
2 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.
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.
- yesterday First seen · 200 lines · 53 tokens per session scan A 6f25ab8029a7
enterprise-java is a skill published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 1,273 once invoked, about $0.0003 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.
Other skills, from other repositories
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
agoragentic-transaction-assurance
Prepare, evaluate, and reconcile autonomous agent transactions without self-granting payment or owner authority. Use when an agent must bind principal authority, seller terms, payment evidence, execution, delivered outcome, and reconciliation; handle paid retries safely; or prepare an authority request for owner…
linkding
Manage bookmarks with Linkding. Use when the user asks to "save a bookmark", "add link", "search bookmarks", "list my bookmarks", "find saved links", "tag a bookmark", "archive bookmark", "check if URL is saved", "list tags", "create bundle", or mentions Linkding bookmark management.
debugging-mutations
Verify what changed on a ServiceNow instance after a tool call — sysaudit inspection, syslog/transaction logs, session context, Flow Designer execution logs, outbound HTTP traces.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).