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/exchanet/method_enterprise_builder_planning/method-enterprise-builder-planningnpx skills add exchanet/method_enterprise_builder_planning --skill method-enterprise-builder-planninggit clone --depth 1 https://github.com/exchanet/method_enterprise_builder_planningWrote 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/exchanet/method_enterprise_builder_planning/method-enterprise-builder-planning)<a href="https://agentmods.dev/skills/exchanet/method_enterprise_builder_planning/method-enterprise-builder-planning"><img src="https://agentmods.dev/badge/skills/exchanet/method_enterprise_builder_planning/method-enterprise-builder-planning.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.1 | $0.00000 | $0.01928 |
| Opus 5 | $0.00000 | $0.00964 |
| Sonnet 5 | $0.00000 | $0.00386 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
method-enterprise-builder-planning 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 5d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: METHOD-ENTERPRISE-BUILDER-PLANNING
Purpose
Orchestrate the full enterprise software planning methodology. Activates the 8-phase planning cycle for mission-critical, high-availability, and enterprise-grade systems. Integrates Method Modular Design (Core + Packs) with PDCA-T quality cycle.
When to Use
Use this skill when:
- Building any system with enterprise-grade requirements (high load, complex transactions, regulated data)
- Designing mission-critical software (failure has catastrophic consequences)
- Planning high-availability architecture (99.9%+ uptime SLA)
- Working on systems requiring compliance (GDPR, ISO 27001, SOC2, PCI-DSS, HIPAA)
- Implementing ACID-compliant transactional features
- Building security-first modules with audit trail
- Starting any feature that involves >1000 concurrent users
Integration with Other Methods
This skill MUST be used in combination with:
| Method | Role in this skill |
|---|---|
method-modular-design |
All code generated follows Core + Packs pattern |
metodo-pdca-t |
PDCA-T cycle applied to EVERY micro-task |
ENTERPRISE_ARCHITECTURE rule |
Architecture decisions and ADR format |
ENTERPRISE_SECURITY rule |
STRIDE, RBAC, audit trail, OWASP checklist |
ENTERPRISE_SCALABILITY rule |
HA patterns, SLA/SLO, caching, circuit breakers |
ENTERPRISE_COMPLIANCE rule |
ACID, ISO 27001, SQuaRE, GDPR, CMMI |
ENTERPRISE_TESTING rule |
Test pyramid, coverage gates, performance tests |
ENTERPRISE_MICROTASK_PLANNER rule |
Decomposition algorithm and backlog format |
Trigger Commands
This skill activates when the user says:
"Plan enterprise feature: [description]"
"Design mission-critical [system type]"
"Create ACID-compliant module for [feature]"
"Build high-availability [component]"
"Implement security-first [module] with audit trail"
"Plan [system] with GDPR / SOC2 / ISO 27001 compliance"
"Activate METHOD-ENTERPRISE-BUILDER-PLANNING"
"Design scalable [system] for [N] concurrent users"
What ships with it
7 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.
- 5d ago First seen · 234 lines · 0 tokens per session scan A 2780ed98969c
method-enterprise-builder-planning is a skill published in the GitHub repository exchanet/method_enterprise_builder_planning (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,928 tokens. 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
033-architecture-diagrams
Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams, ER (Entity Relationship) diagrams, and bounded-context diagrams — through a modular, step-based interactive process that adapts to your…
112-java-maven-plugins
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) …
documentation-patterns
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
810-regulations-eu-mifid-ii
Use when reviewing Java enterprise evidence for MiFID II investment services, investment activities, client classification, suitability, appropriateness, order-handling evidence, best-execution evidence, algorithmic-trading governance evidence, market-access governance evidence, transaction evidence, record keeping…
811-regulations-eu-market-abuse-regulation
Use when reviewing, designing, or modifying Java enterprise systems that may support EU Market Abuse Regulation concerns, market surveillance, suspicious order and transaction reports, insider dealing controls, unlawful disclosure controls, market manipulation detection, inside information disclosure workflows…
803-regulations-gdpr
Use when reviewing, designing, or modifying Java enterprise systems that process personal data and need GDPR-aware engineering controls. This should trigger for requests such as Review a Java service for GDPR privacy controls; Design data-subject rights workflows; Add retention, deletion, pseudonymization, or…