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 hexacron/claude-transformatron-9000 --skill maltego-transform-designgit clone --depth 1 https://github.com/hexacron/claude-transformatron-9000Wrote 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/hexacron/claude-transformatron-9000/maltego-transform-design)<a href="https://agentmods.dev/skills/hexacron/claude-transformatron-9000/maltego-transform-design"><img src="https://agentmods.dev/badge/skills/hexacron/claude-transformatron-9000/maltego-transform-design/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/hexacron/claude-transformatron-9000/maltego-transform-design"><img src="https://agentmods.dev/badge/skills/hexacron/claude-transformatron-9000/maltego-transform-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00034 | $0.00908 |
| Opus 5 | $0.00017 | $0.00454 |
| Sonnet 5 | $0.00007 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
maltego-transform-design 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 8d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maltego Transform Design Skill
Purpose
Guide agents through designing Maltego transforms for a data source before writing any code. Produce a clear design covering entities, transform sets, settings, and investigator workflows.
Step-by-Step Design Process
1. Understand the Data Source
- What objects does the API return? (domains, IPs, people, events, etc.)
- What are the natural investigative pivots? (e.g., domain → IPs, IP → domains, email → person)
- What parameters does the API require? (API keys, search terms, pagination tokens)
2. Map to Standard Entities FIRST
Always check maltego-transforms-std-entities before inventing custom entities.
- Load
references/standard-entity-selection.mdfor entity categories, import patterns, and selection guidance. - Import from
maltego.entities(e.g.,from maltego.entities import Domain, Person, IPv4Address). These classes ship in themaltego-transforms-std-entitiespackage. - If a standard entity class fits — use it. Do not create a custom entity for the sake of it.
3. Propose Custom Entities Only When Needed
Custom entities are justified only when:
- No standard entity class matches the concept.
- The data has meaningful properties that standard entities cannot carry.
- The entity would genuinely be pivoted on in investigations (not just a data container).
Document proposed custom entities with: name, display name, properties, and why no standard entity fits.
4. Design Transform Sets
Group transforms by investigative flow:
- Name each transform set by its input → output concept (e.g., "Domain Enrichment", "Person Lookup").
- Each transform set = one input entity type → one or more output entity types.
- The input and output entity types you design here must be reflected in each transform's
type annotations (first parameter for input; return annotation for output, using a union
when a transform emits more than one type) — those annotations are what
/api/v3/transformspublishes and what the client routes on. - Identify which transforms are independent vs. chained.
What ships with it
1 file 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.
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.
- 8d ago First seen · 81 lines · 34 tokens per session scan A a92d028f981d
maltego-transform-design is a skill published in the GitHub repository hexacron/claude-transformatron-9000 (0 stars, last pushed 21d ago), licensed MIT. It adds 34 tokens to every session and 908 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…