Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/PMDevSolutions/Aureliusnpx agentmods add skills/pmdevsolutions/aurelius/indesign-conversionWrote 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/pmdevsolutions/aurelius/indesign-conversion)<a href="https://agentmods.dev/skills/pmdevsolutions/aurelius/indesign-conversion"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/indesign-conversion/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/pmdevsolutions/aurelius/indesign-conversion"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/indesign-conversion.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.00000 | $0.01022 |
| Opus 5.5 | $0.00000 | $0.00409 |
| Sonnet 5.5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
indesign-conversion 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 yesterday.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
InDesign Conversion
Overview
This skill drives the InDesign pipeline end to end: it parses an exported IDML package or PDF into a normalized intermediate representation (IR), maps the styles and swatches to design tokens (a Tailwind preset, tokens.css, tokens.ts, and a Style Dictionary JSON), and generates typed React components with Storybook stories. It pairs with the indesign-to-react agent, which reviews the generation report and proposes follow-ups.
When to use
- A designer delivered an exported
.idmlor.pdf(the normal handoff) and you want a styled React starting point rather than rebuilding by hand. - You need design tokens (colors, type scale, spacing) derived directly from the InDesign document.
Do not use it for live Figma/Canva designs (use those pipelines) or when you need pixel-perfect reconstruction — this produces a usable, token-driven scaffold for manual refinement.
Prerequisites
- An exported
.idml(File → Export → InDesign Markup) or a PDF exported from InDesign. Source.inddfiles are not supported — export first. - The
@aurelius/pipelinepackage built (pnpm --filter @aurelius/pipeline build). - For best fidelity, prefer IDML when available — it carries named paragraph/character styles and swatches that PDF lacks.
Expected outputs
Into <output> (default ./src/indesign):
*.tsx— one typed component per spread, plus*.stories.tsxand anindex.tsbarrel.tokens/—tokens.ts,tokens.css,tailwind.preset.ts,design-tokens.json.public/indesign/— extracted images, referenced by the components.indesign-pipeline-report.mdandindesign-pipeline-report.json— produced files, staged assets, unmapped frames, and accessibility TODOs.
Worked example
Using the committed fixture (tests/fixtures/indesign/sample.idml):
pnpm --filter @aurelius/pipeline build
node packages/pipeline/dist/pipeline-cli.js pipeline indesign \
tests/fixtures/indesign/sample.idml \
--target react --styling tailwind --output ./out/indesign
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.
- yesterday Changed · +1 lines 31e9b49144b5
- 1mo ago First seen · 65 lines · 0 tokens per session scan A bbbcdf8dca43
indesign-conversion is a skill published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,022 tokens. 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-09-04.
Other skills, from other repositories
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
Figma Developer
Extract components from Figma, convert designs to React components, sync design tokens, and generate code from designs. Bridge the gap between design and code with automated workflows.
high-plains-drifter
Align a design to your real Storybook components instead of reconstructing it. Use when turning a Figma frame into React built from an existing component library (Build mode), or when pulling scrappy exploratory code into line with the library once a direction feels right (Align mode). Triggers include "build this…
figma-build
Build a Figma design from code or a description — the reverse of figma-codegen. Reuses the connected file's existing design system (components, variables, styles) instead of drawing primitives with hardcoded values. Triggers whenever the user wants something created or updated IN Figma from code or a spec — e.g.…
figma-to-code
Generate production-ready React/Next.js code from Figma designs. Instructs proper Figma MCP tool usage, component reuse strategies, and variant mapping. CRITICAL: ALWAYS use this skill when user provides a Figma link or mentions implementing/redesigning from Figma design. Never attempt manual implementation without…
vibefigma
Convert Figma designs to production-ready React components with Tailwind CSS. Use when user provides a Figma URL, asks to convert Figma designs to React/code, wants to extract components from Figma, or mentions "vibefigma". Requires a Figma access token (via --token flag, FIGMATOKEN env var, or .env file).