system-overview

system-overview is a skill for Claude Code, Codex from bromso/metapowers. It costs 72 tokens per session (333 once invoked), scanned A, original, MIT.

Summarize a Figma file's design system — components, styles, token collections and modes, and page structure — in one structured overview. Use when the user is new to a Figma design system or wants to know what it contains before working with it. Not for exporting tokens as code; see /design:export-tokens.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Install with agentmods
npx agentmods add skills/bromso/metapowers/system-overview
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.

Any agent
npx skills add bromso/metapowers --skill system-overview
Clone the repo
git clone --depth 1 https://github.com/bromso/metapowers

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 system-overview

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/bromso/metapowers/system-overview"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/system-overview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 333 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 unknown 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.00072 $0.00333
Opus 5.5 $0.00029 $0.00133
Sonnet 5.5 $0.00014 $0.00067
Haiku 4.5 $0.00007 $0.00033

Measured today against content hash b9bdf474f4c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

system-overview 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 today.

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/skills/system-overview/SKILL.md · 32 lines

What it actually says

System Overview

Get a comprehensive overview of the design system in a Figma file.

Process

  1. Identify the Figma file. The user should provide a file key or URL.

  2. Fetch the design system summary:

    • Call figma_get_design_system_summary to get counts and page structure
    • Call figma_get_styles to list all published styles
    • Call figma_get_components to list all published components
    • Call figma_get_variables with exportFormat: "json" to get token structure
  3. Compile the overview:

    • File info: Name, last modified, page count
    • Components: Total count, listed by name with descriptions
    • Styles: Counts by type (fill, text, effect, grid), listed with names
    • Tokens: Collection count, variable count by type (color, float, string, boolean), mode names
    • Structure: Page names and what each page contains
  4. Present the overview to the user in a clear, structured format.

Output

A structured design system overview presented to the user, useful for onboarding or auditing the design system state.

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. today First seen · 32 lines · 72 tokens per session scan A b9bdf474f4c4

Subscribe to this mod's changes

system-overview is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 333 once invoked, about $0.0003 per session on Opus 5.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-10-21.

Related

Other skills, from other repositories