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/weekly-recap)<a href="https://agentmods.dev/commands/opensesh/design-ops/weekly-recap"><img src="https://agentmods.dev/badge/commands/opensesh/design-ops/weekly-recap/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/weekly-recap"><img src="https://agentmods.dev/badge/commands/opensesh/design-ops/weekly-recap.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.00295 |
| Opus 5.5 | $0.00000 | $0.00118 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
weekly-recap 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 1mo 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:weekly-recap
Legacy alias for /design-ops:dashboard weekly
Trigger
User invokes /design-ops:weekly-recap at the end of a week to review accomplishments and plan ahead.
Behavior
This command is a backwards-compatible alias. It delegates to the unified dashboard command:
/design-ops:weekly-recap → /design-ops:dashboard weekly
Execution
- Invoke
/design-ops:dashboard weekly - Return the weekly dashboard output (all enabled pillars)
Migration Notice
/design-ops:weekly-recap continues to work for backwards compatibility, but the recommended command is now:
/design-ops:dashboard weekly # All pillars, weekly
/design-ops:dashboard ops weekly # Operations only, weekly
/design-ops:dashboard design weekly # Design only, weekly
See /design-ops:dashboard for full documentation on pillar and timeframe options.
Why This Alias Exists
- Muscle memory — Existing users know
/design-ops:weekly-recap - 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 weekly
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.
- 1mo ago First seen · 50 lines · 0 tokens per session scan A b03ba7639055
weekly-recap is a command published in the GitHub repository opensesh/DESIGN-OPS (23 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 295 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.
naksha-help
Quick-reference for any Naksha command — browse by category or look up a specific command.
ux-audit
Audit a Figma file against a design brief — checks page structure, frame naming, sizes, styles, components, and content compliance.
orchestrate
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
nyann:diff-profile
Compare two nyann profiles side-by-side and show what changes between them: hooks, branching, CI, documentation, extras, governance. Useful before switching profiles to understand the impact.