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/naksha-help)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/naksha-help"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/naksha-help/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/naksha-help"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/naksha-help.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.00017 | $0.02425 |
| Opus 5.5 | $0.00007 | $0.00970 |
| Sonnet 5.5 | $0.00003 | $0.00485 |
| Haiku 4.5 | $0.00002 | $0.00243 |
Grade A, and why
naksha-help 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/naksha-help
Contextual quick-reference for Naksha. Browse commands by category or look up a specific one.
Usage:
/naksha-help— show all categories with command counts/naksha-help <category>— list commands in a category/naksha-help <command>— show reference card for a specific command
Categories: design · figma · qa · social · email · data-viz · ai · print · frontier · memory · meta
Step 1: Parse Arguments
Parse $ARGUMENTS:
- Empty → show Category Overview (Step 2A)
- Matches a category name (
design,figma,qa,social,email,data-viz,ai,print,frontier,memory,meta) → show Category Commands (Step 2B) - Matches a command name (with or without leading
/) → show Command Card (Step 2C) - Unclear → show Category Overview with note
Step 2A: Category Overview
Display when no arguments are given:
━━━ Naksha Quick Reference ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Your virtual design team — 30 roles, 70 commands, 7 agents
CATEGORIES Run /naksha-help <category>
design Core design & review 11 commands
figma Figma-native workflows 8 commands
qa Quality & audit 4 commands
social Social media 3 commands
email Email design 3 commands
data-viz Charts & dashboards 3 commands
ai AI visual generation 5 commands
print Print & PDF 3 commands
frontier Conversational, Spatial, AR, Compliance 8 commands
memory Project memory & pipelines 8 commands
meta Templates, tutorial, help 6 commands
━━━ Popular starting points ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
/design Design anything — the main command
/design-review Audit for accessibility & usability issues
/naksha-init Set up project memory (brand, framework, tokens)
/pipeline list See available multi-command pipelines
/design-tutorial Interactive guided tour (choose a track)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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 · 278 lines · 17 tokens per session scan A 1addb9e08ae6
naksha-help is a command published in the GitHub repository Adityaraj0421/naksha-studio (341 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 2,425 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
code-explainer
Use when a designer needs to understand code that already works. What a file does, what a line means, which parts are safe to change. Plain language with Figma analogies, no developer jargon.
setup-guide
Use when someone is starting from nothing and the terminal is unfamiliar. Installing Node and Claude Code, creating a first project, and what to do when a command fails.
help
Complete command reference for DESIGN-OPS.
weekly-recap
Legacy alias for /design-ops:dashboard weekly.
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
alt
Import an Exam Radar (OPTIMETA Alt plugin) export and fold its lecture-emphasis exam signal into the course index — radar.md, a lecture-emphasis column on coverage.md, and a gold-zone weakmap.