design-system: Skill for Claude Code

.agents/skills/repo-maintenance/SKILL.md

repo-maintenance is a skill for Claude Code, Codex from iress/design-system. It costs 86 tokens per session (5,340 once invoked), scanned A, original, Apache-2.0.

A maintenance guide for the Iress Design System, a shared library of interface components and styles, stored in one repository called a monorepo. It covers bugs, tokens, releases, CI, documentation, and reviews.

In plain words
What is it for?
Use it when fixing IDS bugs, updating design tokens, managing dependencies or releases, troubleshooting automated builds, reviewing pull requests, or maintaining documentation.
Why use it?
It gives maintainers a consistent way to handle changes, check regressions, and keep the library and its documentation aligned.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is iress/design-system's own configuration. It tells Claude Code and Codex how to work on design-system itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything design-system configures →

Reuse

Borrowing it

Nothing to install: this file belongs to iress/design-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/iress/design-system/main/.agents/skills/repo-maintenance/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/iress/design-system

Made for: Claude Code, Codex.

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 repo-maintenance

README.md
[![agentmods](https://agentmods.dev/badge/skills/iress/design-system/repo-maintenance/github.svg)](https://agentmods.dev/skills/iress/design-system/repo-maintenance)
Your own site
<a href="https://agentmods.dev/skills/iress/design-system/repo-maintenance"><img src="https://agentmods.dev/badge/skills/iress/design-system/repo-maintenance/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.

agentmods 80×15 button for repo-maintenance

Your own site · 80×15
<a href="https://agentmods.dev/skills/iress/design-system/repo-maintenance"><img src="https://agentmods.dev/badge/skills/iress/design-system/repo-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,340 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00086 $0.05340
Opus 5 $0.00043 $0.02670
Sonnet 5 $0.00017 $0.01068
Haiku 4.5 $0.00009 $0.00534

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

Security

Grade A, and why

repo-maintenance 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 11d 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.

.agents/skills/repo-maintenance/SKILL.md · 448 lines

How it starts

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

Skill: IDS Repo Maintenance

Purpose

Help maintainers perform day-to-day tasks in the IDS monorepo — fixing bugs, managing releases, reviewing PRs, fixing CI, and keeping documentation in sync.

Triage & Prioritisation

During this period, the focus is bug fixes only — no new features, no regressions.

flowchart TD
    A[Incoming request] --> B{What type?}
    B -->|Bug report| C[Ask user to create\nGitHub issue using\nbug_report template]
    B -->|Feature request| D[Features are paused —\nask user to create issue\nusing feature_request template\nfor future prioritisation]
    B -->|New component proposal| D
    B -->|Consumer question| E[Point to Storybook docs\nor relevant agent skill]

    C --> F[Issue created with\nversion, repro steps,\nexpected vs actual]
    F --> G{Large visual\nregression?}
    G -->|Yes — layout shift,\ntheme breakage,\ncomponent redesign| H[Escalate to\nDesign team before\nany code changes]
    G -->|No — functional bug| I[Assign issue to\nGitHub Copilot]
    I --> J[Copilot bug-fixing agent\nanalyses, creates repro story,\nfixes, and opens PR]
    J --> K[Review the PR]
    K --> L{PR looks good?\nTests pass?\nNo regressions?}
    L -->|Yes| M[Merge → CI auto-releases\nif version was bumped]
    L -->|No| N[Leave review comments,\nre-assign to Copilot]
    N --> J

Key rules:

  • Bug fixes are the priority — fix what's broken, prevent regressions
  • Features are paused — ask requesters to file a feature_request or new-component-proposal issue so we can validate the approach when the team is at full capacity
  • Large visual regressions (layout shifts, theme breakage, component redesigns) need Design team sign-off before merging
  • For functional bugs: users create a GitHub issue using the bug_report template (.github/ISSUE_TEMPLATE/bug_report.md), then assign it to Copilot
  • Copilot's bug-fixing agent will solve issues autonomously — see docs/COPILOT-AGENT-SETUP.md for setup and usage
  • Cross-branch bugs use labels (affects-main, affects-5.x, affects-both-branches) — the Copilot agent handles this automatically, see .github/CROSS_BRANCH_LABELS.md

Read the full file on GitHub · 448 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 448 lines · 86 tokens per session scan A 5adb0009dc69

Subscribe to this mod's changes

repo-maintenance is a skill published in the GitHub repository iress/design-system (1 stars, last pushed today), licensed Apache-2.0. It adds 86 tokens to every session and 5,340 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

add-error-tracking

Add Temps error tracking to applications using the Sentry-compatible SDK. Temps exposes a Sentry-compatible DSN that works with the official Sentry SDK for each language/framework — no code changes beyond initialization are required. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue…

gotempsh/temps · 182 tokens

add-react-analytics

Add Temps analytics to React applications with comprehensive tracking capabilities including page views, custom events, scroll tracking, engagement monitoring, session recording, and Web Vitals performance metrics. Use when the user wants to: (1) Add analytics to a React app (Next.js App Router, Next.js Pages Router…

gotempsh/temps · 167 tokens

add-session-recording

Add privacy-aware session recording and replay to React applications using the Temps SDK. Captures user interactions for playback while respecting privacy through input masking, element blocking, and GDPR-compliant consent flows. Use when the user wants to: (1) Add session recording to their app, (2) Implement session…

gotempsh/temps · 148 tokens

temps-design-system

Build or review console UI so it reads as Temps: the paper-and-ink operator design system (@temps-sdk/ds primitives, the operator ink v1 skin, the Ledger / Detail / Settings page templates, the status vocabulary and the record recipe). Invoke when a task adds or redesigns a console screen, a landing section or a…

gotempsh/temps · 148 tokens

deploy-to-temps

Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration. Supports Next.js, Vite, React, Node.js, Python, Go, Rust, Java, and C# applications. Use when the user wants to: (1) Deploy their app to Temps, (2) Set up CI/CD with Temps, (3) Configure…

gotempsh/temps · 141 tokens

bun-sveltekit

Use when building or running SvelteKit apps on Bun, including SSR, adapters, and Bun-specific APIs.

secondsky/claude-skills · 26 tokens