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 commands/opensesh/design-ops/resetgit 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/reset)<a href="https://agentmods.dev/commands/opensesh/design-ops/reset"><img src="https://agentmods.dev/badge/commands/opensesh/design-ops/reset.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.00000 | $0.00709 |
| Opus 5 | $0.00000 | $0.00354 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
reset 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-ops:reset
Reset DESIGN-OPS configuration to start fresh.
Trigger
User runs /design-ops:reset to clear configuration and start over.
Purpose
Use this command when:
- Configuration is corrupted or causing issues
- Want to reconfigure from scratch
- Testing setup flow changes
- Discovery cache is stale and needs refresh
Flow
Step 1: Confirm Intent
## Reset DESIGN-OPS Configuration
This will:
• Back up your current config to ~/.claude/design-ops-config.yaml.backup.{timestamp}
• Remove the current configuration file
• Clear any cached discovery data
Your MCP servers will NOT be affected — only the DESIGN-OPS config.
Are you sure you want to reset?
[Yes, reset configuration] [Cancel]
Step 2: Backup Existing Config
If config exists, create timestamped backup:
if [ -f ~/.claude/design-ops-config.yaml ]; then
cp ~/.claude/design-ops-config.yaml \
~/.claude/design-ops-config.yaml.backup.$(date +%Y%m%d%H%M%S)
fi
Step 3: Remove Config
rm -f ~/.claude/design-ops-config.yaml
Step 4: Confirm Success
## ✓ Configuration Reset
Your DESIGN-OPS configuration has been cleared.
**Backup created:** ~/.claude/design-ops-config.yaml.backup.{timestamp}
**Next steps:**
• Run `/design-ops:setup` to reconfigure
• Or restore your backup if this was a mistake
To restore backup:
```bash
cp ~/.claude/design-ops-config.yaml.backup.{timestamp} \
~/.claude/design-ops-config.yaml
---
## Options
### --no-backup
Skip backup creation (not recommended):
```bash
/design-ops:reset --no-backup
--force
Skip confirmation prompt:
/design-ops:reset --force
Error Handling
No Config Found
No configuration found at ~/.claude/design-ops-config.yaml
Nothing to reset. Run `/design-ops:setup` to create a new configuration.
Backup Failed
Could not create backup. Check permissions for ~/.claude/
To reset anyway (without backup):
/design-ops:reset --no-backup
Or fix permissions and try again.
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 · 149 lines · 0 tokens per session scan A ecef522e3e5d
reset 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 709 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-compliance
Audit or generate regulation-specific UI patterns for HIPAA, PCI DSS, or ADA compliance. Use --regulation to target a specific standard.
design-gdpr
Design GDPR/CCPA-compliant consent flows — cookie banners, consent hierarchy, privacy controls, and data deletion request UI.
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
design-voice-ui
Design a voice interface — wake word flows, confirmation patterns, error recovery, screen companion layout (if hybrid), audio feedback guidelines.
design-chatbot
Design a complete chatbot or conversational assistant UI — dialog flows, message bubbles, quick replies, typing indicators, error states, and accessibility.
design-review
Review an existing design for quality — accessibility, usability, visual consistency, content, and motion. Accepts HTML files, Figma URLs, preview servers, or screenshots for visual AI critique.