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/opensesh/DESIGN-OPSWrote 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/opensesh/design-ops/configure)<a href="https://agentmods.dev/commands/opensesh/design-ops/configure"><img src="https://agentmods.dev/badge/commands/opensesh/design-ops/configure.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.00000 | $0.02134 |
| Opus 5 | $0.00000 | $0.01067 |
| Sonnet 5 | $0.00000 | $0.00427 |
| Haiku 4.5 | $0.00000 | $0.00213 |
Grade A, and why
configure 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 7d 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-ops:configure
Update specific settings without running full setup. Pillar-based configuration with re-evaluation options.
Trigger
User runs /design-ops:configure to modify existing configuration.
Can also target specific pillars:
/design-ops:configure operations/design-ops:configure design/design-ops:configure analytics/design-ops:configure team
Pre-Flight Check
-
Check for config at
~/.claude/design-ops-config.yaml- If not found: "No config found. Run
/design-ops:setupfirst to get started." - Exit early
- If not found: "No config found. Run
-
Check version
- If v1.x: "Found v1 config. Run
/design-ops:setupto migrate to v2 first." - If v2.x: Continue
- If v1.x: "Found v1 config. Run
-
Load current config and validate structure
Main Menu
## Configure DESIGN-OPS
**Current status:**
- Operations: 2 tools (Notion, Google Workspace)
- Design: 2 tools (GitHub, Figma)
- Analytics: 2 tools (GA4, Dub.co), 1 skipped
What would you like to configure?
Options:
Operations pillar— Modify operations tools and outcomesDesign pillar— Modify design tools and outcomesAnalytics pillar— Modify analytics tools and outcomesTeam members— Add/edit/remove team mappingsDisplay preferences— Time windows, output optionsAdd new tool— Trigger/design-ops:add-toolRe-evaluate all tools— Re-run tool evaluationView full config— Show complete YAML
Pillar Configuration
Operations Pillar
## Operations Pillar Configuration
**Connected tools:**
┌──────────────────┬───────────┬─────────────────────────────┐
│ Tool │ Status │ Tracking │
├──────────────────┼───────────┼─────────────────────────────┤
│ Notion │ Connected │ 3 databases │
│ Google Workspace │ Connected │ Calendar, Gmail │
│ Slack │ Skipped │ — │
└──────────────────┴───────────┴─────────────────────────────┘
**Current outcomes:**
- Daily: calendar_events, tasks_due, unread_emails
- Weekly: week_overview, tasks_completed
What would you like to do?
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.
- 7d ago First seen · 416 lines · 0 tokens per session scan A 26800b57588f
configure is a command published in the GitHub repository opensesh/DESIGN-OPS (23 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,134 tokens. 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
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
design-template
Generate a production-ready web page from a curated template category. Pick a category (landing-page, dashboard, pricing, auth, blog, ecommerce, portfolio, docs, saas, or onboarding) and get a fully-built, customized HTML/CSS template — brand colors, copy, and responsive layout included.
figma-component-library
Generate a complete component library in Figma from a design system config — atoms, molecules, and organisms with all variants, auto layout, and component properties.
naksha-doctor
Run all naksha quality checks and report the plugin's health status.
naksha-browse
Browse any URL with browser vision — extract design patterns for research or inspect your own UI, saved to project memory.
dashboard-layout
Design and build a complete dashboard layout — sidebar navigation, KPI cards, chart areas, data tables, filter bar, and responsive behavior. Outputs production-ready HTML/CSS.