hex-architecture SKILL.md skillA
hex-architecture from wntic/pyhouse is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wntic/pyhouse/hex-architecture@git:20261014.20fc6e0Pins git:20261014.20fc6e0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wntic/pyhouse
- Path
plugins/pyhouse-hex/skills/hex-architecture/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261014.20fc6e0, committed Oct 14, 2026
- First version recorded
- Oct 11, 2026
- Size
- 19,280 bytes
- Repository stars
- 3
- License
- MIT
Use when the family is already settled as hexagonal and the question is where a module belongs or whether an import may cross a boundary — the four layers, inward-only dependencies, ports, adapters, the composition root. Not whether hexagonal is the right family at all (`architecture-choice`), not where a boundary goes in the first place (`coupling`). - Which layer does this class go in; may infrastructure import application; a cycle between layers; where the DI container or composition root…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Hexagonal Architecture — the layer contract Which layer a thing belongs to, and what it is allowed to reach. This skill owns boundaries only: the mechanics of packaging a module and spelling an import are `python-packaging`, and they are the same here as in any other project. What goes *inside* a module belongs to whichever skill owns that artifact. ## When to use vs. neighbours - Whether this style is the right one at all, or the service belongs in the flat-layered family → `architecture-choice`, which owns the hex-vs-flat decision in full and is universal, so it is available whichever family plugins are installed. - The family is settled the other way — a worker, crawler, pipeline or integration service grouped by technical role, with no ports until a second real implementation → `flat-layered`, in the `pyhouse-flat` plugin. Nothing in this skill applies there. - Where a boundary goes at all — split vs merge, whether an integration needs a contract, how much structure a component deserves → `coupling`, loaded alongside this skill; it owns the boundary reasoning, this skill owns the layer layout. …
Read the whole file at its exact version.
How to install
mdr add wntic/pyhouse/hex-architecture@sha256:a2d092532c19ebe6The line at the top of this page pins the label git:20261014.20fc6e0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_l3p27oq7qtzzwdlh)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 11, 2026 and Oct 14, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.20fc6e0 latest | 2026-10-14 | 20fc6e0 | 19,280 B | A | view · diff |
| git:20261011.122368f | 2026-10-11 | 122368f | 19,237 B | A | view · diff |
| git:20261011.4a676ac | 2026-10-11 | 4a676ac | 19,230 B | A | view · diff |
| git:20261011.5611761 | 2026-10-11 | 5611761 | 19,241 B | A | view · diff |
| git:20261011.ee4b568 | 2026-10-11 | ee4b568 | 19,199 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (19280 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wntic/pyhouse · 3 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l3p27oq7qtzzwdlh GET https://markdownregistry.com/api/v1/resolve?ref=wntic/pyhouse/hex-architecture GET https://markdownregistry.com/api/v1/blob/a2d092532c19ebe6bf5c9a1b3a16cc55b673b581af8c434c53ede64afed4cdfd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.