add-machine
Skill1 starsChanged 14 days agoMITView on GitHub
Procedimiento para crear o modificar una Machine (secuencia automática de transforms con etapas, rondas y presupuestos) en maltego-mcp, predefinida en código o propia en el catálogo TOML. Úsala para automatizar un flujo de reconocimiento.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- danielrosehill/Claude-Security-Auditor-Plugintheir own version, first seen Apr 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- danielrosehill/Claude-Security-Auditor-Plugin★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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
- 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
The file
Files
Añadir una Machine
- Semántica: cada etapa aplica sus transforms a todo lo descubierto en la ronda (
accumulate=True); con varias rondas, la frontera siguiente son las entidades nuevas. Las cadenas ad hoc (transforms=[...]) aplican cada paso solo a lo del paso anterior. - Predefinida: añade
Machine(nombre, descripción, input_types, stages)aBUILTIN_MACHINESensrc/maltego_mcp/machines.pyy, si es la natural para un tipo, aDEFAULT_MACHINE_BY_TYPE. - Propia del usuario (sin código; equivale a
register_machinede otros MCP: semilla =input_types, transforms por etapa =stages, límite de expansión =rounds), en~/.maltego-mcp/transforms.toml:[[machines]] name = "MiRecon" input_types = ["maltego.Domain"] stages = [["DNSToIP", "DomainToNS"], ["IPToAS"]] rounds = 1 - Incluye transforms de proveedores sin miedo: si falta la clave se omiten y se informa en
unavailable. - Tests: en
tests/test_copilot.pycon elRoutersimulado; comprueba etapas, que no se repite un transform sobre la misma entidad y el presupuestomax_total_entities. - Documenta la Machine en
README.md,README.es.md,docs/USO.mdyCHANGELOG.md.
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.

