save-patterns

save-patterns is a command for Claude Code from joaquimscosta/arkhe-claude-plugins. It costs 14 tokens per session (852 once invoked), scanned A, original, MIT.

A command that reviews recent development work and suggests design patterns worth keeping as part of the project's design intent.

In plain words
What is it for?
It can review component patterns, layout choices, spacing, typography, colours, and other design decisions, then suggest where to document them. Use it with an optional category such as components, foundations, or layouts.
Why use it?
It helps find reusable decisions before they are forgotten, while leaving the final decision and documentation to the developer.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the design-intent plugin — 4 skills, 5 commands, 3 agents shipped together

Install

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.

agentmods
npx agentmods add commands/joaquimscosta/arkhe-claude-plugins/save-patterns
Clone the repo
git clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-plugins

Made for: Claude Code.

Or install design-intent, the plugin that ships this one along with the rest of its 4 skills, 5 commands, 3 agents.

Wrote 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.

agentmods badge for save-patterns

README.md
[![agentmods](https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/save-patterns.svg)](https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/save-patterns)
Your own site
<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/save-patterns"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/save-patterns.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 852 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00852
Opus 5 $0.00007 $0.00426
Sonnet 5 $0.00003 $0.00170
Haiku 4.5 $0.00001 $0.00085

Measured 6d ago against content hash d94dc027a3e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

save-patterns 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 6d 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.

plugins/design-intent/commands/save-patterns.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/save-patterns

Purpose: Analyze recent work and suggest design patterns that should be preserved as design intent

Usage: /save-patterns [category]

Examples:

  • /save-patterns - Analyze all recent work for patterns
  • /save-patterns components - Focus on component patterns only
  • /save-patterns foundations - Focus on spacing, typography, color patterns
  • /save-patterns layouts - Focus on layout and grid patterns

What This Command Does

  1. Reviews Recent Work - Analyzes code changes, components created, and design decisions made in the current session
  2. Identifies Reusable Patterns - Finds design decisions that could benefit other features
  3. Suggests Documentation Locations - Recommends where each pattern should be documented (components/, foundations/, patterns/)
  4. Presents Summary for Review - Shows findings to user for manual decision-making
  5. Waits for User Direction - Does NOT automatically document anything

Analysis Focus

The agent will look for:

Custom Design Decisions

  • Layout patterns that deviate from standard design system
  • Spacing decisions that aren't standard tokens
  • Component compositions unique to your application
  • Content hierarchies and information architecture patterns

Reusable Components

  • Custom components created during implementation
  • Extensions to existing components
  • Component variations that could be reused

Responsive Patterns

  • Breakpoint-specific behaviors
  • Mobile optimization strategies
  • Layout adaptations across screen sizes

Visual Treatments

  • Color usage beyond design system tokens
  • Typography treatments for specific contexts
  • Shadow, border, and elevation patterns

Output Format

The agent will present findings as:

## Design Intent Candidates

### Components Patterns
- **CustomDataCard** → `components/data-card.md`
  - Reason: Unique hover states and nested action buttons
  - Reusability: High - used in 3+ contexts

### Foundation Patterns
- **48px Section Spacing** → `foundations/custom-spacing.md`
  - Reason: Consistent spacing between major page sections
  - Reusability: Medium - applies to L1 layouts

### Layout Patterns
- **Three-Column Dashboard** → `patterns/dashboard-layout.md`
  - Reason: Specific grid system for dashboard pages
  - Reusability: High - dashboard variations

## Not Recommended for Documentation
- Standard Fluent spacing tokens (already in design system)
- Default component behaviors (documented in Fluent)

Read the full file on GitHub · 114 lines

Changes

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.

  1. 6d ago First seen · 114 lines · 14 tokens per session scan A d94dc027a3e8

Subscribe to this mod's changes

save-patterns is a command published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 22d ago), licensed MIT. It adds 14 tokens to every session and 852 once invoked, about $0.0001 per session on Opus 5. 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.