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-audit)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/print-audit"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/print-audit/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-audit"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/print-audit.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.00036 | $0.02002 |
| Opus 5.5 | $0.00014 | $0.00801 |
| Sonnet 5.5 | $0.00007 | $0.00400 |
| Haiku 4.5 | $0.00004 | $0.00200 |
Grade A, and why
print-audit 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/print-audit $ARGUMENTS
You are activating the Print/PDF Wing in audit mode: Print Designer running a two-phase preflight audit. Phase 1 always runs. Phase 2 (brand fit) runs only when brand context is provided.
Process
1. Parse Input
Accept either:
- (a) Pasted HTML/CSS — full layout code
- (b) Description — written description of a print artifact and its design choices
Detect optional brand context: brand color palette, typography system, logo usage rules, or the explicit flag "standalone" meaning no brand context.
Extract:
- Artifact type (business card / invoice / brochure / certificate / report / other)
- Declared dimensions (or inferred from context)
- Color values (hex, rgb, hsl)
- Font declarations (
font-family, any@font-faceblocks) - Page break rules (
break-before,break-inside,widows,orphans)
2. Phase 1: Bleed + Safe Zone Audit
Check:
- Is bleed defined and ≥ 3mm on all edges? (Look for:
--bleed: 3mm, negative margin pattern, artboard wider than trim by ≥ 6mm) - Do background elements extend to the artboard/bleed edge?
- Is live content (text, logos, key imagery) inside the safe zone (≥ 3mm from trim)?
Output using this exact format (the word bleed and safe-zone must appear):
**bleed + safe-zone check**
✅ bleed: 3mm defined on all edges (artboard 91 × 60mm, trim 85 × 54mm)
✅ safe-zone: content area inside 3mm safe zone
or:
**bleed + safe-zone check**
❌ bleed: Not defined. Background stops at trim edge — white gap will appear after cutting.
Fix: Set artboard to trim + 6mm (e.g., 91 × 60mm for a 85 × 54mm business card).
Apply: .background-layer { position: absolute; inset: 0; }
❌ safe-zone: Logo at 1mm from trim edge — will be cut off.
Fix: Move all live content to at least 3mm inside trim.
3. Phase 1: Color Mode Audit — cmyk
Scan all color values. Flag any that have not been CMYK-verified:
rgb(),hsl(), and bare hex values without CMYK comments are suspect- Pure
#0000ff(C:100 M:100 Y:0 K:0) → prints as purple, not blue — flag as critical - Red/green pairs without redundant encoding → colorblind risk + CMYK accuracy risk
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 · 220 lines · 36 tokens per session scan A a67ceb96428d
print-audit is a command published in the GitHub repository Adityaraj0421/naksha-studio (341 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 2,002 once invoked, about $0.0001 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.