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 organvm-iv-taxis/a-i--skills --skill domain-ideal-whole-substrategit clone --depth 1 https://github.com/organvm-iv-taxis/a-i--skillsWrote 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/organvm-iv-taxis/a-i--skills/domain-ideal-whole-substrate)<a href="https://agentmods.dev/skills/organvm-iv-taxis/a-i--skills/domain-ideal-whole-substrate"><img src="https://agentmods.dev/badge/skills/organvm-iv-taxis/a-i--skills/domain-ideal-whole-substrate/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/organvm-iv-taxis/a-i--skills/domain-ideal-whole-substrate"><img src="https://agentmods.dev/badge/skills/organvm-iv-taxis/a-i--skills/domain-ideal-whole-substrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 249 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00109 | $0.03901 |
| Opus 5 | $0.00055 | $0.01951 |
| Sonnet 5 | $0.00022 | $0.00780 |
| Haiku 4.5 | $0.00011 | $0.00390 |
Grade A, and why
domain-ideal-whole-substrate 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 12d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Ideal-Whole Substrate (DIWS)
The substrate beneath every flag-pierce. Where Product Domain Engine (PDE) handles the product layer (logos / ethos / pathos / kairos), this skill handles the domain layer beneath. Every domain — chess, fitness, voodoo, education, design — composes from the same eight strata under the same four operators, with load distribution shifting by domain.
User's foundational question: "What elements, systems, structures, environments, agents so forth make the ideal whole (be it fitness, chess, or voodoo)?"
DIWS answers it as substrate, not as workflow.
What This Is
A substrate, not a workflow. PDE is a 5-phase formalization protocol that consumes a domain and produces a product. DIWS is what the domain itself is before any product gets built on top of it. PDE pulls from DIWS substrate; DIWS does not pull from PDE.
DIWS does two things PDE cannot:
- Cross-portfolio reuse — Phase 0 audits
~/Workspace/for existing engines (3-tier taxonomy: domain / meta / consultant) before any new domain instantiates. Engine + skin pattern, not from-scratch every time. - Stretching rack — Phase 0.5 runs the gap-map operator across N concurrent DIWS instances simultaneously. Surfaces holes (under-developed dimensions) and fat (redundant scaffolding) at portfolio scale, not just per-domain.
You invoke this skill when a flag has been pierced or is about to be — a friend's domain, a research interest, a consulting engagement, a side practice. The goal is to load the substrate ahead of any product-building work so that PDE / synthesis / cross-pollination diagnoses operate over filled scaffolding rather than empty types.
Invariants
These hold across every flag-pierce, regardless of domain:
- Phase 0 portfolio-audit runs BEFORE layer-1 ontology — never scratch-build what an existing engine can re-skin (rule 41: audit before building)
- Phase 0.5 engine-overlap board comes between Phase 0 and layer-1 — visualize candidate engines + gaps before scaffolding (rule 36: seed not specification)
- All 8 strata instantiate — even if a stratum is sparse for the domain (load shifts, layers don't disappear)
- All 4 operators fire on every instantiation — selfish-altruistic + magnetic + portfolio + reflexive (Tenet Protocol — both directions simultaneously)
- Layer 4 (gap-map) and Layer 8 (contribution) close as a loop — heist + contribute round-trip; never steal without giving back
- Layer 8 produces dissertation-grade research output — academic capital is substrate, not garnish
- Reflexive Operator produces
domain-meta-study.mdalongside the 8 stratum artifacts — every build co-arises with a study-of-build - Capital flow is N-channel, not 1-channel — monetary is one of many; meta-skill capital, audience cross-flow, tool extraction, work-improvement all count
What ships with it
44 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.
- assets/domain-agent-fleet-template.yaml 4.2 KB
- assets/domain-agent-fleet.yaml 0 B
- assets/domain-attractor-template.md 2.6 KB
- assets/domain-attractor.md 135 B
- assets/domain-constellation-template.yaml 2.3 KB
- assets/domain-constellation.yaml 335 B
- assets/domain-contribution-charter-template.md 3.3 KB
- assets/domain-contribution-charter.md 157 B
- assets/domain-gap-map-template.md 2.3 KB
- assets/domain-gap-map.md 131 B
- assets/domain-lineage-template.md 2.9 KB
- assets/domain-lineage.md 131 B
- assets/domain-meta-study-template.md 3.0 KB
- assets/domain-meta-study.md 137 B
- assets/domain-ontology-template.md 1.6 KB
- assets/domain-ontology.md 404 B
- assets/domain-production-stack-template.md 2.0 KB
- assets/domain-production-stack.md 149 B
- assets/engine-overlap-board.md 143 B
- assets/portfolio-resonance-template.md 3.0 KB
- assets/portfolio-reuse-map.md 141 B
- proof-instances/chess/domain-constellation.yaml 3.1 KB
- proof-instances/chess/domain-gap-map.md 4.3 KB
- proof-instances/chess/domain-meta-study.md 5.2 KB
- proof-instances/chess/domain-ontology.md 4.3 KB
- proof-instances/chess/README.md 1.3 KB
- proof-instances/education/domain-meta-study.md 4.8 KB
- proof-instances/education/domain-ontology.md 3.8 KB
- proof-instances/education/README.md 1.7 KB
- proof-instances/voodoo/domain-contribution-charter.md 6.4 KB
- proof-instances/voodoo/domain-meta-study.md 6.2 KB
- proof-instances/voodoo/domain-ontology.md 4.9 KB
- proof-instances/voodoo/README.md 1.8 KB
- proof-instances/wellness/domain-meta-study.md 5.6 KB
- proof-instances/wellness/domain-ontology.md 4.4 KB
- proof-instances/wellness/README.md 1.3 KB
- references/4-operators-spec.md 7.2 KB
- references/8-strata-spec.md 10 KB
- references/diws-msp-mapping.md 6.3 KB
- references/engine-taxonomy.md 7.2 KB
- references/portfolio-composition-map.md 7.6 KB
- scripts/audit-portfolio.sh 7.7 KB runs code
- scripts/audit.sh 758 B runs code
- scripts/portfolio-gap-audit.sh 9.2 KB runs code
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.
- 12d ago First seen · 262 lines · 109 tokens per session scan A 7f9a1a6779f5
domain-ideal-whole-substrate is a skill published in the GitHub repository organvm-iv-taxis/a-i--skills (17 stars, last pushed 16d ago), licensed Apache-2.0. It adds 109 tokens to every session and 3,901 once invoked, about $0.0005 per session on Opus 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-30.
Other skills, from other repositories
agent-communication-protocol
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks.
agent-creation-skill
Procedural guide for creating new agents from templates when project complexity requires delegation.
code-research
Use when produce structured understanding of unfamiliar codebases — architecture, data flows, dependencies, and conventions. Use when joining a new project, tracing feature implementations, or mapping system architecture.
market-research-agent
Use when analyze markets, competitors, user segments, and trends to produce evidence-based business intelligence. Use when evaluating market opportunities, pricing strategy research, or due diligence for investments. Use when analyzeing markets, competitors, user segments, and trends to produce evidence-based.
model-strategy
Multi-model orchestration and model-switching strategy. Score-based model selection, reasoning-effort routing, cross-agent delegation (Gemini, Codex, Ollama), advisor pairing, escalation triggers, permission matrix, and cost-efficiency optimization.
skypilot-multi-cloud-orchestration
Multi-cloud orchestration for ML workloads with automatic cost optimization. Use when you need to run training or batch jobs across multiple clouds, leverage spot instances with auto-recovery, or optimize GPU costs across providers.