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/team-pulse)<a href="https://agentmods.dev/commands/opensesh/design-ops/team-pulse"><img src="https://agentmods.dev/badge/commands/opensesh/design-ops/team-pulse.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.00544 |
| Opus 5 | $0.00000 | $0.00272 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
team-pulse 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 8d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-ops:team-pulse
Legacy alias for /design-ops:dashboard design daily with team focus
Trigger
User invokes /design-ops:team-pulse to see who's working on what across Figma and GitHub.
Behavior
This command is a backwards-compatible alias. It delegates to the unified dashboard command with team-focused output:
/design-ops:team-pulse → /design-ops:dashboard design daily --team
Execution
- Invoke
/design-ops:dashboard design dailywith team member breakdown - Return the design dashboard with emphasis on:
- Activity by team member
- Team snapshot table
- Who's working on what
Team Focus Flag
The --team modifier enhances the design dashboard to include:
### Team Snapshot
| Person | Design | Code |
|--------|--------|------|
| {Name} | {N} files | {N} commits |
| {Name} | — | {N} commits, {N} PRs |
This flag is automatically applied when using /design-ops:team-pulse.
Migration Notice
/design-ops:team-pulse continues to work for backwards compatibility, but the recommended command is now:
/design-ops:dashboard design daily # Design pillar, daily timeframe
/design-ops:dashboard design weekly # Design pillar, weekly summary
The team snapshot table is included in design dashboards when team members are configured.
See /design-ops:dashboard for full documentation on pillar and timeframe options.
Prerequisites
For best results, configure team members in ~/.claude/design-ops-config.yaml:
team:
members:
- name: "Jordan Smith"
handles:
figma: "jordan.smith"
github: "jordansmith"
- name: "Taylor Lee"
handles:
figma: "taylor.lee"
github: "taylorl"
Run /design-ops:configure → Team to update team member mappings.
Why This Alias Exists
- Muscle memory — Existing users know
/design-ops:team-pulse - Semantic clarity — "Team pulse" clearly communicates team activity focus
- Gradual migration — Users can adopt new syntax at their own pace
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.
- 8d ago First seen · 90 lines · 0 tokens per session scan A e44f37e49212
team-pulse 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 544 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.
design-handoff
Generate a developer handoff document from a Figma file — spacing specs, token maps, component APIs, and production-ready code snippets.
data-viz-audit
Audit a data visualization for chart type selection, accessible color palette, annotations, and anti-patterns. Optionally audits dashboard layout fit when context is provided. Outputs a scored checklist and corrected code.