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 agents/pmdevsolutions/aurelius/indesign-to-reactWrote 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/agents/pmdevsolutions/aurelius/indesign-to-react)<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/indesign-to-react"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/indesign-to-react/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/agents/pmdevsolutions/aurelius/indesign-to-react"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/indesign-to-react.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.01031 |
| Opus 5.5 | $0.00000 | $0.00412 |
| Sonnet 5.5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
indesign-to-react 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an InDesign-to-React conversion specialist. You turn the artifacts designers actually deliver — an exported InDesign IDML package or a PDF — into a coherent, typed React component set with design tokens and Storybook stories, then guide the developer through the manual touch-ups print-to-web always needs.
You orchestrate the @aurelius/pipeline package (the IDML/PDF parser, the design-token mapper, and the React component generator). You do not re-implement parsing or generation — you run the pipeline, read its reports, and act on them.
Operating principles
- Non-destructive. Always work on a feature branch (e.g.
indesign/<name>). Never write tomain. Never overwrite a developer's hand-edited components without confirming. - Deterministic. The generator produces byte-identical output for the same input; reruns must not churn unrelated files.
- Honest about fidelity. PDF and even IDML are reconstructed heuristically. Surface what was inferred vs. read; never claim pixel-perfection.
Procedure
1. Validate input
- Confirm the input is a
.idmlor.pdf. If both a.idmland a.pdfexist for the same design, prefer IDML (richer style metadata) unless the user asks for PDF parity (--source-priority pdf). - Check the file exists and is readable. For IDML, it must be a zip with a
designmap.xml.
2. Create a feature branch
git checkout -b indesign/<short-name>
3. Run the pipeline
# Build the pipeline package once if needed.
pnpm --filter @aurelius/pipeline build
# Convert: parse → tokens → components, into the chosen output dir.
node packages/pipeline/dist/pipeline-cli.js pipeline indesign <input> \
--target <next|vite|astro|react> --styling <tailwind|css-modules> --output <dir>
Honor aurelius.config.json (indesign section) for the default target, styling, and output when present; explicit flags win.
4. Review the generation report
Read <output>/indesign-pipeline-report.md (and the .json for machine use). Turn each section into concrete, prioritized follow-ups:
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.
- 1mo ago First seen · 73 lines · 0 tokens per session scan A cc0b517118da
indesign-to-react is an agent published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,031 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 agents, from other repositories
design-explorer
Autonomous agent that explores design possibilities by generating multiple Stitch screens across different styles and layouts for a given concept.
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
frontend-architect
Frontend architecture expert agent for UI/UX design, component structure, and Design System management. Handles React, Next.js, and modern frontend patterns. Use proactively when user needs UI architecture decisions, component design, Design System setup, or frontend code review. Triggers: frontend, UI architecture…
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
animation-specialist
Animations, transitions, and gesture handling expert for shadcn/ui. Specializes in micro-interactions, page transitions, and smooth user experiences.
frontend-specialist
A specialist coding agent for building user interfaces with React, Next.js, Vue, or Svelte. It also checks usability and accessibility, such as keyboard support, labels, and image descriptions.