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 xonovex/platform --skill orthogonal-pattern-guidegit clone --depth 1 https://github.com/xonovex/platformWrote 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/xonovex/platform/orthogonal-pattern-guide)<a href="https://agentmods.dev/skills/xonovex/platform/orthogonal-pattern-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/orthogonal-pattern-guide/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/xonovex/platform/orthogonal-pattern-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/orthogonal-pattern-guide.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.00098 | $0.00833 |
| Opus 5.5 | $0.00039 | $0.00333 |
| Sonnet 5.5 | $0.00020 | $0.00167 |
| Haiku 4.5 | $0.00010 | $0.00083 |
Grade A, and why
orthogonal-pattern-guide 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 1mo 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orthogonal Axes
Decompose around independent decisions likely to change. An axis names the question; each variant is one answer. A configuration chooses one variant per axis.
Essentials
- Find independent decisions: derive axes from what can vary separately, not execution steps, see references/finding-axes.md
- Separate commonality from variability: keep only truly shared rules at the axis root and put each answer in a leaf, see references/commonality-variability.md
- Make the tree reveal the model: use one directory per axis and bare, symmetric variant names, see references/applying-the-layout.md, references/naming-symmetry.md
- Localize cross-axis constraints: place exceptional two-axis glue in the dependent variant, see references/variation-point-bridges.md
- Distinguish cross-cutting concerns: apply concerns that touch every selection once around the composed operation, see references/cross-cutting-concerns.md
- Align ownership and change: a change to one concept should stay inside one axis and one owner, see references/boundary-alignment.md
Handoffs
- Use hexagonal-pattern-guide to design the ports and adapters that enforce a chosen axis.
- Use microkernel-pattern-guide to implement registration, discovery, capability gating, and binding time.
- Use connascence-guide to grade and loosen coupling across a proposed seam.
- Use ddd-guide to discover bounded contexts and domain vocabulary before drawing domain boundaries.
Gotchas
- Two choices that always change together are one axis; splitting them creates permanent synchronization work.
- A concern present in every configuration is cross-cutting, not another selectable variant.
- Do not extract an axis for one hypothetical implementation. Wait for independent change pressure or a real second variant.
- A tidy tree is false modularity when leaves still import siblings or share hidden mutable state; enforce the dependency rules owned by hexagonal-pattern-guide and assess violations with connascence-guide.
What ships with it
11 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.
- eval-queries.json 7.9 KB
- evals.json 3.0 KB
- moon.yml 166 B
- references/applying-the-layout.md 1.2 KB
- references/boundary-alignment.md 931 B
- references/commonality-variability.md 981 B
- references/cross-cutting-concerns.md 956 B
- references/finding-axes.md 1.6 KB
- references/naming-symmetry.md 950 B
- references/variation-point-bridges.md 987 B
- SOURCES.md 6.1 KB
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.
- 1mo ago First seen · 42 lines · 98 tokens per session scan A 1801bed3404b
orthogonal-pattern-guide is a skill published in the GitHub repository xonovex/platform (6 stars, last pushed 4d ago), licensed MIT. It adds 98 tokens to every session and 833 once invoked, about $0.0004 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-09-08.
Other skills, from other repositories
harbor-daytona
Use Harbor's Daytona sandbox platform for computer use — creating sandboxes, taking screenshots, sending mouse/keyboard input, and building agent loops. Use when the user wants to interact with a GUI, automate a desktop, do computer use, control a browser visually, or run Claude computer use against a Daytona sandbox.
docker
Use when authoring or auditing a Dockerfile, shrinking a bloated image, hardening a container that runs as root, picking a base image, or wiring a Compose dev loop with hot reload. NOT CI builds or deploy-to-host (that is deployment), NOT k8s autoscaling (that is scaling), NOT app-level injection or secrets-in-code…
kastell
Server security auditing, hardening, and fleet management. 457 security checks across 30 categories (SSH, Firewall, Docker, TLS, HTTP Headers), CIS/PCI-DSS/HIPAA compliance mapping, 24-step production hardening, and 13 MCP tools. Supports Hetzner, DigitalOcean, Vultr, and Linode with Coolify, Dokploy, and bare VPS…
ilo
Run builds, tests, and other tooling inside a reproducible, containerized dev environment via the ilo CLI instead of on the host. Use this whenever a project relies on ilo, devcontainers, or container-based build environments — it has a .ilo.rc / .ilo/ilo.rc, dev/ argument files, a Containerfile/Dockerfile, a…
docker-compose-local-setup
Creates or updates local multi-service orchestration using docker compose. Covers compose.yaml design, service health checks, dependson readiness, env files, named volumes, migrations/seeds jobs, verification commands, and cleanup workflows for local development.
compose
A guide to Docker Compose, a tool for defining and running applications made of multiple containers, such as a web app, API, and database.