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/daily-brief)<a href="https://agentmods.dev/commands/opensesh/design-ops/daily-brief"><img src="https://agentmods.dev/badge/commands/opensesh/design-ops/daily-brief/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/opensesh/design-ops/daily-brief"><img src="https://agentmods.dev/badge/commands/opensesh/design-ops/daily-brief.svg" alt="Reviewed on agentmods" width="80" 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.00290 |
| Opus 5 | $0.00000 | $0.00145 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
daily-brief 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 10d 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
/design-ops:daily-brief
Legacy alias for /design-ops:dashboard daily
Trigger
User invokes /design-ops:daily-brief to start their day with a consolidated view.
Behavior
This command is a backwards-compatible alias. It delegates to the unified dashboard command:
/design-ops:daily-brief → /design-ops:dashboard daily
Execution
- Invoke
/design-ops:dashboard daily - Return the daily dashboard output (all enabled pillars)
Migration Notice
/design-ops:daily-brief continues to work for backwards compatibility, but the recommended command is now:
/design-ops:dashboard # All pillars, daily (default)
/design-ops:dashboard daily # Explicit daily timeframe
/design-ops:dashboard ops daily # Operations only, daily
See /design-ops:dashboard for full documentation on pillar and timeframe options.
Why This Alias Exists
- Muscle memory — Existing users know
/design-ops:daily-brief - Documentation links — Prevents broken references
- Gradual migration — Users can adopt new syntax at their own pace
Version: 2.0 (alias wrapper) Delegates to: /design-ops:dashboard daily
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.
- 10d ago First seen · 50 lines · 0 tokens per session scan A aecb5abacc58
daily-brief 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 290 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-browse
Browse any URL with browser vision — extract design patterns for research or inspect your own UI, saved to project memory.
naksha-doctor
Run all naksha quality checks and report the plugin's health status.
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.