maltego-formats
Skill1 starsChanged 14 days agoMITView on GitHub
Referencia de los formatos de Maltego que usa maltego-mcp (protocolo XML de transforms TRX/iTDS, grafos .mtgx, configuraciones .mtz, transforms locales y ontología .entity). Úsala al leer, generar o depurar cualquiera de estos ficheros o el puente con Maltego Desktop.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-builtin-transformSkill
- add-machineSkill
- company-footprintSkill
- custom-providerSkill
- external-osint-toolsSkill
- hybrid-deploymentSkill
- identity-footprintSkill
- infrastructure-mappingSkill
- ioc-graph-compositionSkill
- maltego-formatsSkill
- mcp-tool-changeSkill
- non-standard-entitiesSkill
- osint-investigationSkill
- releaseSkill
- security-reviewSkill
- add-builtin-transformSkill
- add-machineSkill
- company-footprintSkill
- custom-providerSkill
- external-osint-toolsSkill
- hybrid-deploymentSkill
- identity-footprintSkill
- infrastructure-mappingSkill
- ioc-graph-compositionSkill
- mcp-tool-changeSkill
- non-standard-entitiesSkill
- osint-investigationSkill
- releaseSkill
- security-reviewSkill
The file
Files
Formatos de Maltego
Transforms TRX/iTDS (transforms/protocol.py): POST de XML a /run/<nombre>/, donde el nombre es el de la
clase en minúsculas con _ → - (convención de maltego-trx). Petición MaltegoMessage/MaltegoTransformRequestMessage
(una entidad con Value, AdditionalFields, Limits SoftLimit, TransformFields). Respuesta
MaltegoTransformResponseMessage (entidades + UIMessages) o MaltegoTransformExceptionMessage. Propiedades de
enlace con prefijo link# (maltego.link.label, maltego.link.direction=output-to-input).
.mtgx (maltego/mtgx.py): ZIP con Graphs/Graph1.graphml. Nodos con mtg:MaltegoEntity type=... y
mtg:Properties/mtg:Property name/displayName/type + mtg:Value; posición en mtg:EntityRenderer/mtg:Position;
aristas con mtg:MaltegoLink type="maltego.link.manual-link" y la etiqueta en maltego.link.manual.type.
maltego-mcp añade maltego_mcp/investigation.json (memoria), que Maltego ignora. URL y Document muestran
short-title/title, pero el valor real está en url.
.mtz (maltego/bridge.py, cli.py): ZIP de configuración. Transforms locales generados con
maltego_trx.decorator_registry.TransformRegistry.write_local_mtz (Servers/Local.tas,
TransformRepositories/Local/*.transform|.transformsettings, TransformSets/*.set). Entidades en
Entities/*.entity (<MaltegoEntity id=...><Properties value="propiedad principal">).
Transforms locales: Maltego ejecuta comando parámetros valor "k=v#k2=v2"; solo reciben valor y propiedades
(no el tipo), por eso hay un transform puente por tipo. La salida XML va por stdout en UTF-8.
Lecturas siempre acotadas y con defusedxml (ver read_mtgx, inspect_mtgx).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.