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.
git clone --depth 1 https://github.com/Adityaraj0421/naksha-studioWrote 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/commands/adityaraj0421/naksha-studio/print-layout)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/print-layout"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/print-layout/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/commands/adityaraj0421/naksha-studio/print-layout"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/print-layout.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.00040 | $0.01455 |
| Opus 5.5 | $0.00016 | $0.00582 |
| Sonnet 5.5 | $0.00008 | $0.00291 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
print-layout 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 today.
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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/print-layout $ARGUMENTS
You are activating the Print/PDF Wing in layout mode: Print Designer, producing a single print artifact with correct bleed/safe zone setup, CMYK color documentation, and print-ready HTML/CSS.
Process
1. Parse Input
Extract from $ARGUMENTS:
- Artifact type: business card / flyer / certificate / brochure / invoice / other
- Brand name: for color and logo references
- Dimensions: use standard for artifact type if not specified (see reference table in
print-designer.md) - Finish: coated / uncoated / digital-only (affects CMYK richness recommendations)
Set artboard: trim + 3mm bleed on all sides. Example: business card trim 85 × 54mm → artboard 91 × 60mm.
2. Canvas + Bleed Setup
:root {
--trim-w: 85mm; /* adjust per artifact */
--trim-h: 54mm;
--bleed: 3mm;
--safe: 3mm;
}
.artboard {
width: calc(var(--trim-w) + 2 * var(--bleed));
height: calc(var(--trim-h) + 2 * var(--bleed));
position: relative;
overflow: hidden;
}
/* Guide marks — screen only */
@media screen {
.trim-guide {
position: absolute;
inset: var(--bleed);
border: 0.5px dashed #9ca3af;
pointer-events: none;
z-index: 999;
}
.safe-guide {
position: absolute;
inset: calc(var(--bleed) + var(--safe));
border: 0.5px dotted #d1d5db;
pointer-events: none;
z-index: 999;
}
}
@media print {
.trim-guide, .safe-guide { display: none; }
}
3. Grid + Safe Zone
Define the column grid inside the safe zone (not inside the trim):
.content-area {
position: absolute;
inset: calc(var(--bleed) + var(--safe));
/* All live content (text, logos) goes in here */
}
.background-layer {
/* Backgrounds and decorative elements: extend to artboard edge */
position: absolute;
inset: 0;
background: var(--brand-primary);
-webkit-print-color-adjust: exact;
print-color-adjust: exact;
}
4. CMYK Color System
Map brand colors to CMYK-safe hex equivalents and document in CSS:
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.
- today First seen · 174 lines · 40 tokens per session scan A 7678ac44ef6f
print-layout is a command published in the GitHub repository Adityaraj0421/naksha-studio (341 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,455 once invoked, about $0.0002 per session on Opus 5.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-10-19.
Other commands, from other repositories
print-export-designer
Use when something has to leave the screen. PDF generation, print stylesheets, receipts and invoices, exported reports, or a download that gives the user no feedback.
brand
Generate a full editorial brand-guidelines book for any URL. 14 chapters covering brand essence/archetype, colour, typography, spacing, shape, iconography, motion, components, voice, accessibility, tokens, and how-to-use guidance. Print-ready, dark-mode toggle, hand-off-ready single HTML.
pack
Bundle every designlang output (DTCG tokens, Tailwind, shadcn, Figma vars, motion, anatomy, Storybook, prompts) into one polished design-system directory ready to zip and ship.
add-library
Kullanıcı "kütüphane ekle", "library ekle", "tasarım sistemi ekle", "design system ekle" dediğinde bu komutu uygula.
design-enforce
Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.
design-grill
Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.