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.
npx agentmods add instructions/adityaraj0421/naksha-studio/agents-mdgit 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/instructions/adityaraj0421/naksha-studio/agents-md)<a href="https://agentmods.dev/instructions/adityaraj0421/naksha-studio/agents-md"><img src="https://agentmods.dev/badge/instructions/adityaraj0421/naksha-studio/agents-md.svg" alt="Measured on agentmods" 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 | $0.00220 | $0.00220 |
| Opus 5 | $0.00110 | $0.00110 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
naksha-studio AGENTS.md 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 5d 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.
What it actually says
Naksha Design Team — Autohand Code CLI
This file activates the Naksha virtual design team when working in
Autohand Code CLI. Naksha's canonical skill lives in
skills/design/SKILL.md; use that orchestrator for any design, UI/UX,
visual, branding, spatial, conversational, or compliance task.
How to Use Naksha
- Read
skills/design/SKILL.mdfirst. - Follow its routing guidance to select the right design roles and reference files.
- Use the files under
skills/design/references/as the source of truth for specialist design knowledge. - For command-style workflows, read the matching file in
commands/and execute that process directly.
Operating Rules
- Keep outputs production-ready: responsive, accessible, polished, and specific to the user's product context.
- Prefer existing Naksha role references over inventing new guidance.
- When changing Naksha itself, follow
CONTRIBUTING.mdand keep platform adapters in sync.
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.
- 5d ago First seen · 25 lines · 220 tokens per session scan A 81e430ebff7b
naksha-studio AGENTS.md is an instructions file published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 220 tokens to every session, about $0.0011 per session on Opus 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-08-30.
Other instructions, from other repositories
ui-ux-suite CLAUDE.md
Claude Code instructions for Aboudjem/ui-ux-suite, covering project, constraints, technology stack, recommended stack and ci/cd: github actions.
cannonball AGENTS.md
Instructions for harebeats/cannonball, covering cannonball — para qualquer agente, o que você precisa saber para operar, onde ficam os dados, a ordem que dá melhor resultado and ferramentas de agente citadas.
designer-pro-and-seo AGENTS.md
Instructions for ZachArticulateV/designer-pro-and-seo, covering core operating principles, skill families and when to reach for them, parallel build pattern (encoded once, reused everywhere), qa gate as mandatory pre-delivery and routing law (no model reviews its own output).
figma-design-skills AGENTS.md
Instructions for jeltehomminga/figma-design-skills, covering agents.md, the two skills, core rules (both skills), scope boundary and requirements.
ultimate.UIUX.design.skills AGENTS.md
Instructions for ca-who-codes/ultimate.UIUX.design.skills, covering agents.md — design pro, your role, how to use the knowledge base (progressive disclosure), the design loop and non-negotiables (apply to everything).
forge-skills CLAUDE.md
Claude Code instructions for aneja5/forge-skills, covering forge-skills, project structure, the .forge/ handoff chain, skills by phase and conventions.