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/ux-audit)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/ux-audit"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/ux-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/ux-audit"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/ux-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.00027 | $0.01621 |
| Opus 5.5 | $0.00011 | $0.00648 |
| Sonnet 5.5 | $0.00005 | $0.00324 |
| Haiku 4.5 | $0.00003 | $0.00162 |
Grade A, and why
ux-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 2d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-audit
You are running a compliance audit of a Figma file against a design brief. This checks whether a Figma deliverable meets all specified requirements.
Input: $ARGUMENTS
Process
1. Parse the Brief
Extract structured requirements from the user's brief text. Look for:
| Category | What to extract |
|---|---|
| Pages | Required page names, count, ordering |
| Frames | Frame naming conventions, required sizes (e.g., 1440×900) |
| Components | Required component types, variant states, naming patterns |
| Styles | Required color palette (hex values), text styles (font, size, weight) |
| Content | Required sections, headings, text content, annotations |
| Variables/Tokens | Required design tokens, variable collections |
| Naming | Specific naming conventions (e.g., S3-A, Brand/Primary) |
If the brief is unclear on specifics, state your assumptions before auditing.
2. Connect to Figma
figma_get_status → verify connection
figma_get_file_data(depth: 1, verbosity: 'summary') → get file overview
If not connected, guide the user to open the Desktop Bridge plugin.
3. Structural Audit
Check page and frame structure against requirements:
// Get all pages
figma_execute: `
const pages = figma.root.children.map(p => ({
name: p.name,
id: p.id,
childCount: p.children.length
}));
return pages;
`
For each required page:
- Does it exist with the correct name?
- Does it contain the expected frames?
For each required frame:
- Check name matches exactly
- Check dimensions:
frame.widthandframe.height - Check it's on the correct page
4. Style Audit
Check Figma styles against requirements:
// Get all local styles
figma_execute: `
const paintStyles = (await figma.getLocalPaintStylesAsync()).map(s => ({
name: s.name,
id: s.id,
paints: s.paints
}));
const textStyles = (await figma.getLocalTextStylesAsync()).map(s => ({
name: s.name,
id: s.id,
fontSize: s.fontSize,
fontName: s.fontName
}));
return { paintStyles, textStyles };
`
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.
- 2d ago First seen · 229 lines · 27 tokens per session scan A c22690e3d923
ux-audit is a command published in the GitHub repository Adityaraj0421/naksha-studio (343 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 1,621 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
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.
dna
Place a design in the measured design space — nearest systems, per-axis percentiles, outliers.
extract
Extract the complete design language from a URL — DTCG tokens, Tailwind, Figma vars, motion, voice, components.
fidelity
Measure how faithfully a clone reproduces a site — pixel-diff plus motion-fidelity into one 0-100 score, a letter grade, a ranked correction plan, and a shareable card.
site
Crawl a whole site and synthesize ONE canonical design system across all pages — unified tokens, coverage map, consistency grade.
theme-swap
Recolour an extracted site's design around a new brand primary. OKLCH hue rotation preserves perceptual lightness — neutrals, type, spacing, and motion stay untouched. Side-by-side HTML preview + recoloured tokens (DTCG, Tailwind, shadcn, Figma).