Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Adityaraj0421/naksha-studio/plugin install 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/design-gdpr)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-gdpr"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-gdpr.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.1 | $0.00025 | $0.04533 |
| Opus 5 | $0.00013 | $0.02266 |
| Sonnet 5 | $0.00005 | $0.00907 |
| Haiku 4.5 | $0.00003 | $0.00453 |
Grade A, and why
design-gdpr 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 8d 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-gdpr
You are designing a complete GDPR/CCPA-compliant consent and privacy control system. Your output is a single structured spec covering cookie banner variants, consent flow, privacy control center wireframe, data deletion request flow, and a jurisdiction-specific compliance checklist.
Input
Arguments: $ARGUMENTS
Parse the following from $ARGUMENTS:
- Product type: the type of product (e.g., e-commerce, SaaS, media, healthcare portal)
- Jurisdiction:
eu(GDPR) /ca(CCPA) /both(default:both) - Consent categories: one or more of
analytics,marketing,personalization(default: all three)
Step 1: Load Knowledge Base
Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/compliance-designer.md to apply the full Compliance Designer knowledge base to every section below.
MCP Fallback: If the file cannot be read, proceed using inline knowledge. The inline knowledge for this command covers: GDPR Article 7 conditions for consent (affirmative action, freely given, withdrawal as easy as giving), EDPB Guidelines 03/2022 dark patterns (pre-ticked boxes, nudge colors, unequal button prominence, multiple-click rejection), IAB TCF v2.2 Purpose IDs 1–10 (all off by default), CCPA opt-out requirement ("Do Not Sell or Share My Personal Information" footer link, 15-day response window), DSAR flow (identity verification, 30-day response window, extendable by 2 further months for complex requests = 90 days total), and data portability (GDPR Art. 20, machine-readable JSON/CSV).
Step 2: Generate the Spec
Produce all five sections below as a single continuous output. Do not pause or ask for confirmation between sections.
Section 1: Cookie Banner Variants
Generate three cookie banner variants. For each: layout dimensions, typography, button hierarchy, and ARIA requirements. Tailor to the parsed product type and jurisdiction.
Variant A: Minimal
Use case: Low-risk products, returning-user re-consent, supplementary notice layer.
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.
- 8d ago First seen · 419 lines · 25 tokens per session scan A c312cfce2de3
design-gdpr is a command published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 4,533 once invoked, about $0.0001 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 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).