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 plan-enterprisegit 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/plan-enterprise)<a href="https://agentmods.dev/skills/exchanet/method_enterprise_builder_planning/plan-enterprise"><img src="https://agentmods.dev/badge/skills/exchanet/method_enterprise_builder_planning/plan-enterprise/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/plan-enterprise"><img src="https://agentmods.dev/badge/skills/exchanet/method_enterprise_builder_planning/plan-enterprise.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.01140 |
| Opus 5.5 | $0.00006 | $0.00456 |
| Sonnet 5.5 | $0.00003 | $0.00228 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
plan-enterprise 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Plan Enterprise
Purpose
Orchestrate the full METHOD-ENTERPRISE-BUILDER-PLANNING 8-phase cycle for enterprise-grade, mission-critical, and high-availability software systems.
When to use
Activate this skill when the user requests:
- "Plan an enterprise system..."
- "Design a mission-critical [component]..."
- "Build a high-availability [module] with [SLA]..."
- "Architect a security-first [system] with [compliance]..."
Or when the user mentions regulated data (PCI-DSS, GDPR, HIPAA, SOC2, ISO 27001).
Workflow
Phase 1: Enterprise Context Analysis
Actions:
- Classify system (enterprise-grade, mission-critical, high-availability, security-first, ACID-required)
- Build stakeholder map (end users, compliance officer, operations, regulators)
- Map regulatory environment (applicable standards with obligations)
- List integration points (protocol, SLA dependency level)
Output artifact:
- Create
docs/enterprise-context.md(usecreateFileoperation) - Artifact type:
implementation_plan
Gate: Ask user to confirm system classification before proceeding.
Phase 2: Non-Functional Requirements
Actions:
- Define Performance SLOs: throughput (TPS), latency p95/p99
- Define Availability SLA: % uptime, RTO, RPO, deploy strategy
- Define Scalability: initial, peak, growth rate
- Define Security baseline: auth, authz, encryption at rest/transit
- Define Compliance per standard
Gate: All SLOs must be numeric and measurable (not "fast" or "secure" — "p95 ≤ 500ms", "99.9% SLA").
Phase 3: Risk Matrix
Actions:
- STRIDE analysis on primary API surface (Spoofing, Tampering, Repudiation, Info Disclosure, DoS, Elevation of Privilege)
- Technical risk catalog (probability, impact, mitigation)
- Flag any CRITICAL unmitigated risk — blocks Phase 4
Output: docs/risk-matrix.md
Gate: No CRITICAL risk may be unmitigated; all HIGH risks must have mitigations.
Phase 4: Micro-task Decomposition
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 · 154 lines · 16 tokens per session scan A 3aa681e6d9ad
plan-enterprise 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 1,140 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
product-data-cleanup
Clean a local FF&E CSV schedule by normalizing casing, dimensions, units, language, materials, and formatting. Use when asked to clean, fix, or standardize product data.
product-image-processor
Download, resize, and remove backgrounds from product images at scale. Use when the user asks to "process product images", batch-download images from the schedule, strip backgrounds, or standardize product photos.
product-research
Find and compare current FF&E candidates from a design brief, with sourced purchasing facts and optional CSV-library save. Use to research or source products; not to match from an image or pair coordinating items.
product-spec-bulk-fetch
Extract structured FF&E specs from a list of product URLs into a schedule. Use to pull or bulk-import product-page data; not for PDF catalogs.
zoning-envelope
Generate interactive 3D zoning envelope viewers from zoning analysis reports. Use when the user asks to "visualize the zoning envelope" or see buildable massing in 3D, typically after /as:zoning-analysis-nyc. Requires a zoning analysis report as input.
site-history
Neighborhood context and history — adjacent uses, architectural character, landmarks, commercial activity, and planned development from an address. Use when the user asks about a site's history or surroundings, "what's around this site", neighborhood character, or nearby planned development.