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 skills add exchanet/method_enterprise_builder_planning --skill phase-1-contextgit 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/phase-1-context)<a href="https://agentmods.dev/skills/exchanet/method_enterprise_builder_planning/phase-1-context"><img src="https://agentmods.dev/badge/skills/exchanet/method_enterprise_builder_planning/phase-1-context/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/skills/exchanet/method_enterprise_builder_planning/phase-1-context"><img src="https://agentmods.dev/badge/skills/exchanet/method_enterprise_builder_planning/phase-1-context.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.00016 | $0.00608 |
| Opus 5.5 | $0.00006 | $0.00243 |
| Sonnet 5.5 | $0.00003 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
phase-1-context 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 2mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Phase 1 — Enterprise Context Analysis
Purpose
Execute Phase 1 independently: classify the system, map stakeholders, identify regulatory obligations, and list integration points.
When to use
- When starting a new enterprise planning session
- When the user only needs context analysis (not the full 8-phase cycle)
- As a prerequisite before jumping to Phase 3 or Phase 5
Steps
1. System Classification
Ask or infer the classification across 5 dimensions:
| Dimension | Options |
|---|---|
| Grade | Enterprise-grade / Standard |
| Criticality | Mission-critical / Business-critical / Non-critical |
| Availability | HA (99.9%+) / Standard |
| Security | Security-first / Standard |
| Transactions | ACID-required / Eventually consistent / Stateless |
Output:
## System Classification
- [x] Enterprise-grade
- [x] Mission-critical
- [x] High-availability (99.999%)
- [x] Security-first
- [x] ACID-required
2. Stakeholder Map
Identify who cares about this system and what their primary concern is:
| Stakeholder | Role | Key concern |
|---|---|---|
| [Name/role] | End user / Internal / Compliance / Operations / Regulator | [Specific concern] |
3. Regulatory Environment
Map applicable regulations to specific obligations:
| Regulation | Scope | Key obligation |
|---|---|---|
| GDPR | EU personal data | Art. 32: Encryption; Art. 17: Erasure |
| PCI-DSS | Payment card data | Req. 3: No raw PAN; Req. 10: Audit logging |
If no regulations apply, state explicitly: "No regulated data — standard security practices apply."
4. Integration Points
List external systems with protocol and SLA dependency level:
| System | Protocol | SLA dependency |
|---|---|---|
| [System name] | gRPC / REST / Event / SQL | Critical / High / Medium / Low |
Dependency levels:
- Critical: Transaction cannot complete without it
- High: Significant degradation if unavailable
- Medium: Graceful degradation possible
- Low: Fire-and-forget, async
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.
- 2mo ago First seen · 87 lines · 16 tokens per session scan A e93a4cd4f230
phase-1-context is a skill published in the GitHub repository exchanet/method_enterprise_builder_planning (2 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 608 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 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) …
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…
812-regulations-eu-product-liability-directive
Use when reviewing, designing, or modifying Java enterprise software products, AI-enabled products, RAG assistants, AI agents, generated instructions, related services, automated updates, vulnerability handling, corrective updates, warnings, instructions, or product-safety evidence under Directive (EU) 2024/2853, the…
801-regulations-eu-ai-act
Use when reviewing, designing, or modifying Java enterprise systems that use AI, LLMs, AI agents, RAG, tool calling, workflow automation, or model-based decision support and need EU AI Act regulatory awareness. This should trigger for requests such as Review a Java AI system for EU AI Act controls; Design governance…