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/statusgit 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/status)<a href="https://agentmods.dev/commands/opensesh/design-ops/status"><img src="https://agentmods.dev/badge/commands/opensesh/design-ops/status.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.01480 |
| Opus 5 | $0.00000 | $0.00740 |
| Sonnet 5 | $0.00000 | $0.00296 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
status 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-ops:status
Show current configuration status organized by pillars, integration health, and available commands.
Trigger
User runs /design-ops:status to see what's configured and working.
Workflow
Step 1: Load Configuration
-
Read
~/.claude/design-ops-config.yaml -
If not found:
## DESIGN-OPS — Not Configured No configuration found at ~/.claude/design-ops-config.yaml Run `/design-ops:setup` to get started, or see `/design-ops:help` for available commands.Exit early.
-
Check version
- If v1.x: "Found legacy v1 config. Run
/design-ops:setupto migrate to v2." - If v2.x: Continue
- If v1.x: "Found legacy v1 config. Run
-
Parse config and note any issues
Step 2: Check Integration Health
For each pillar, check connected tools:
For MCP connections:
- Try a basic query to verify MCP is responding
- Success → "Connected"
- Timeout → "Not responding"
For API connections:
- Validate token if stored
- Success → "Connected as {handle}"
- Failure → "Token invalid or expired"
Step 3: Render Status
## DESIGN-OPS — Status
**Config version:** 2.0
**Last updated:** April 14, 2025
---
### Operations Pillar
| Tool | Status | Details |
|------------------|-------------|----------------------------|
| Notion | Connected | MCP, 3 databases tracked |
| Google Workspace | Connected | MCP, calendar + email |
| Slack | Not configured | — |
**Daily outcomes:** calendar_events, tasks_due, unread_emails
**Weekly outcomes:** week_overview, tasks_completed
---
### Design Pillar
| Tool | Status | Details |
|--------|-------------|----------------------------|
| GitHub | Connected | MCP, 2 repos tracked |
| Figma | Connected | API, 1 project tracked |
**Daily outcomes:** recent_commits, open_prs, design_updates
**Weekly outcomes:** team_contributions, design_versions
---
### Analytics Pillar
| Tool | Status | Details |
|------------------|-------------|----------------------------|
| Google Analytics | Connected | MCP, GA4 property |
| Dub.co | Connected | MCP, 15 links tracked |
| Substack | Skipped | No wrapper created |
**Daily outcomes:** pageviews, link_clicks
**Weekly outcomes:** traffic_trends, top_links
---
### Team
| Name | Figma | GitHub |
|-------------|--------------|--------------|
| Jordan | jordan.smith | jordansmith |
| Taylor Lee | taylor.lee | taylorl |
---
### Enabled Commands
Based on your connected tools:
- `/design-ops:daily-brief` — Operations + Design + Analytics
- `/design-ops:weekly-recap` — Operations + Design + Analytics
- `/design-ops:team-pulse` — Design (GitHub + Figma)
- `/design-ops:analytics` — Analytics
---
### Config Location
`~/.claude/design-ops-config.yaml`
---
### Quick Actions
- `/design-ops:configure` — Update settings
- `/design-ops:test` — Run diagnostics
- `/design-ops:add-tool` — Connect new tools
- `/design-ops:help` — Command reference
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 · 264 lines · 0 tokens per session scan A 5d43e0040326
status 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 1,480 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
sentinel
GitHub-aware work monitor - triages issues, PRs, and CI failures.
design-compliance
Audit or generate regulation-specific UI patterns for HIPAA, PCI DSS, or ADA compliance. Use --regulation to target a specific standard.
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
design-gdpr
Design GDPR/CCPA-compliant consent flows — cookie banners, consent hierarchy, privacy controls, and data deletion request UI.
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.
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.