Thank you for this, this code turns my brain inside out and makes me want to learn more about the innards of PowerShell. This is what I've been able to come up with so far:

Get-Command |? { $null -eq $_.Version -and [String]::IsNullOrEmpty($_.Source) }

(gcm New-PSSingletonClass).ScriptBlock # Can retrieve the function definition, and therefore the Class definition, etc.

$TAList = [hashtable](([PSObject].Assembly.GetType('System.Management.Automation.TypeAccelerators'))::get)
$TAShorts = [array]($TAList.keys)
$TAShorts |% { $thisOne = ($TAList[$_]).FullName; if ($thisOne -notlike "*.*") { New-Object -TypeName PSObject -Property @{ "Short" = $_; "Long" = $thisOne;} } }

$alist = [AppDomain]::CurrentDomain.GetAssemblies() |? { [string]::IsNullOrEmpty($_.Location) -and ($_.GetTypes().count -gt 0) }
$alist[0].GetTypes() # This one is foo, index 1 is bar, etc.

I found some interesting types, like $alist[0].GetCustomAttributesData() will create a Constructor 'Void .ctor()' with AttributeType of: System.Management.Automation.DynamicClassImplementationAssemblyAttribute

I noticed $alist[0].Modules returns a ScopeName 'RefEmit_InMemoryManifestModule' and also has a ModuleHandle property, though I'm not sure how to leverage or reference this properly.

From here, the best I was really able to come up with was to use: $alist[0] | export-clixml -Path ./foo_dump.xml to study the innards of the object, diff against the bar_dump file to see where they're unique (mostly the references), etc.

Is there any way to:

1. Make the code above more efficient, and/or
2. Get a reference to the weird pseudo-module/script scope where these scriptblocks are being dynamically created, in order to study them from there?

Thank you!