Agent skill

Validate Tokens

by Orange-OpenSource in Orange-OpenSource/Orange-Boosted-Bootstrap

Read-only audit of OUDS design token usage across SCSS component files.

Install Validate Tokens

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill validate-tokens -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap validate-tokens --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/validate-tokens .claude/skills/validate-tokens && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "validate-tokens" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/validate-tokens into .claude/skills/validate-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-tokens", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/validate-tokens

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill validate-tokens -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap validate-tokens --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/validate-tokens .agents/skills/validate-tokens && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "validate-tokens" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/validate-tokens into .agents/skills/validate-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-tokens", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill validate-tokens -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap validate-tokens --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/validate-tokens .cursor/skills/validate-tokens && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "validate-tokens" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/validate-tokens into .cursor/skills/validate-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-tokens", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git --path .github/skills/validate-tokens

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill validate-tokens -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap validate-tokens --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/validate-tokens .gemini/skills/validate-tokens && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "validate-tokens" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/validate-tokens into .gemini/skills/validate-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-tokens", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap validate-tokens

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill validate-tokens -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/validate-tokens .github/skills/validate-tokens && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "validate-tokens" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/validate-tokens into .github/skills/validate-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-tokens", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill validate-tokens -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Orange-OpenSource/Orange-Boosted-Bootstrap validate-tokens --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/validate-tokens .opencode/skills/validate-tokens && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "validate-tokens" agent skill from https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/main/.github/skills/validate-tokens into .opencode/skills/validate-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-tokens", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: validate-tokens
GitHub stars: 222
Token cost: ~620 tokens
SKILL.md length: 129 words
Files: 1
Skills in repo: 13
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Read-only audit of OUDS design token usage across SCSS component files.

Works in 4 steps: Load brand tokens → Identify component SCSS files → For each file → …
The user asks to validate
SKILL.md covers Step 1 — Load brand tokens, Step 2 — Identify component…, Step 3 — For each file and Step 4 — Generate report
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Validate Tokens is an agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. Read-only audit of OUDS design token usage across SCSS component files. Use this skill when the user asks to validate, check, or audit tokens, when reviewing PRs that touch scss/.scss or packages/, or before a release. Performs cross-brand presence check (are tokens defined in all 3 brands?) and anti-pattern detection (hardcoded values, raw tokens, forbidden patterns). Generates a structured report — does not modify files.

Its SKILL.md is about 620 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering CSS and styling and Design tokens. The repository describes itself as: OUDS Web is an accessible, ergonomic and Orange branded framework based on Orange Unified Design System and Bootstrap. The licence is MIT.

When your agent uses it

The user asks to validate
Reviewing PRs that touch scss/.scss
Before a release

Example prompts

“/validate-tokens”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Load brand tokens
Identify component SCSS files
For each file
Generate report

What it can do on your machine

Read from SKILL.md and the folder at commit f25f7be. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Validate Tokens loads about 620 tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 129 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~111
When it runs · the whole SKILL.md, loaded when a task matches: ~620

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Orange-OpenSource/Orange-Boosted-Bootstrap at commit f25f7be, republished under its MIT licence (© Orange-OpenSource). 129 words, ~620 tokens.

Download SKILL.mdSave it as .claude/skills/validate-tokens/SKILL.md (or your agent's skills folder).

name: validate-tokens
description: Read-only audit of OUDS design token usage across SCSS component files. Use this skill when the user asks to validate, check, or audit tokens, when reviewing PRs that touch scss/_*.scss or packages/, or before a release. Performs cross-brand presence check (are tokens defined in all 3 brands?) and anti-pattern detection (hardcoded values, raw tokens, forbidden patterns). Generates a structured report — does not modify files.

Workflow: Validate Token Usage

This is a read-only audit. Generate a report, do not modify files.

Step 1 — Load brand tokens

Read all 3 files and extract $ouds-* definitions:

packages/orange/scss/tokens/_component.scss
packages/sosh/scss/tokens/_component.scss
packages/orange-compact/scss/tokens/_component.scss

Step 2 — Identify component SCSS files

All scss/_*.scss + scss/forms/_*.scss, excluding: _variables.scss, _config.scss, _functions.scss, _mixins.scss, _maps.scss, _root.scss, _reboot.scss, _utilities.scss, _helpers.scss, _grid.scss, _containers.scss, _images.scss, _type.scss, _transitions.scss, _forms.scss, _variables-dark.scss

Step 3 — For each file

Cross-brand check

Find $ouds-<component>-* tokens used as values → verify present in all 3 brands. Skip semantic tokens ($ouds-color-*, $ouds-space-*, etc.) — always present.

Anti-pattern detection

Pattern	Severity
Hardcoded px/rem/em	WARNING
Hardcoded hex color	WARNING
`$core-ouds-*` (raw token)	ERROR
`$core-orange-` / `$core-sosh-`	ERROR
`lighten()` / `darken()`	ERROR
`border: none`	ERROR
Direct `transition:`	ERROR
Direct `border-radius:`	ERROR

Exceptions: standalone 0, @keyframes, comments, 100%, calc() multipliers, // stylelint-disable lines.

Step 4 — Generate report

╔══════════════════════════════════════════════╗
║  OUDS TOKEN VALIDATION REPORT               ║
║  Files analyzed: N                           ║
╚══════════════════════════════════════════════╝

── CROSS-BRAND PRESENCE ────────────────────────
✅ PASS: N files — all tokens in all brands
❌ FAIL: $token-name missing in [brand]

── ANTI-PATTERNS ───────────────────────────────
⚠️  WARNING: file:line → suggestion
❌ ERROR: file:line → fix

── SUMMARY ─────────────────────────────────────
Cross-brand: N pass, N fail
Anti-patterns: N warnings, N errors

Files

Just SKILL.md in .github/skills/validate-tokens of Orange-OpenSource/Orange-Boosted-Bootstrap.

Open the folder on GitHubat commit f25f7be

Compare with similar skills

Validate Tokens next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Validate Tokens compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Validate Tokens this skillOrange-OpenSource/Orange-Boosted-Bootstrap	222	—	~620	Automated safety check: Pass	MIT	today
MCP Developmentcoollabsio/coolify	63k	1 repos	~949	Automated safety check: Pass	MIT	today
Transitions PolishJakubantalik/transitions.dev	4.6k	2 repos	~3.2k	Automated safety check: Pass	Custom licence	yesterday
Web Style ExtractorLucent-Snow/style-extractor	453	—	~3.8k	Automated safety check: Pass	None	6 mo ago
Liuguang Banlan UIsickn33/agentic-awesome-skills	47k	1 repos	~2.5k	Automated safety check: Pass	MIT	yesterday
Tailwind Design SystemSuFxGIT/scoutarr	114	5 repos	~5.6k	Automated safety check: Pass	None	6 mo ago

Similar skills

MCP Development
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
63k GitHub starsUsed in 1 repo~949 tokens
Frontend & DesignAuto-check passed
Transitions Polish
Jakubantalik/transitions.dev
Audits existing UI animations against the transitions.dev motion-token scale and suggests tokens for duration, distance, scale, blur and easing.
4.6k GitHub starsUsed in 2 repos~3.2k tokens
Frontend & DesignAuto-check passed
Web Style Extractor
Lucent-Snow/style-extractor
Extracts evidence-backed style guides and motion appendices from websites, keeping reusable visual language and stripping product-specific content.
453 GitHub stars~3.8k tokensUpdated 6 mo ago
Frontend & DesignAuto-check passed
Liuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
47k GitHub starsUsed in 1 repo~2.5k tokens
Frontend & DesignAuto-check passed
Tailwind Design System
SuFxGIT/scoutarr
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns.
114 GitHub starsUsed in 5 repos~5.6k tokens
Frontend & DesignAuto-check passed
Extract Design
Manavarya09/design-extract
Extract the full design language from any website URL. An agent skill from Manavarya09/design-extract.
4.2k GitHub stars~786 tokensUpdated 8 days ago
Frontend & DesignAuto-check: notes

More from Orange-OpenSource/Orange-Boosted-Bootstrap

All 13 skills in this repo

Token System
Orange-OpenSource/Orange-Boosted-Bootstrap
OUDS design token system rules and architecture. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
222 GitHub stars~780 tokensUpdated today
Auto-check passed
Using Ouds Web Version Major Minor
Orange-OpenSource/Orange-Boosted-Bootstrap
Provides comprehensive knowledge of the OUDS Web library (Orange Unified Design System for Web), a Bootstrap-based CSS/JS framework for building Orange-branded web interfaces.
222 GitHub stars~4.1k tokensUpdated today
Auto-check passed
Code Review
Orange-OpenSource/Orange-Boosted-Bootstrap
OUDS Web compliance code review. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
222 GitHub stars~846 tokensUpdated today
Auto-check passed
Component Patterns
Orange-OpenSource/Orange-Boosted-Bootstrap
SCSS and JS structural patterns for OUDS Web components. An agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap.
222 GitHub stars~773 tokensUpdated today
Auto-check passed
Create Component
Orange-OpenSource/Orange-Boosted-Bootstrap
Step-by-step workflow for creating a new SCSS and/or JavaScript component in OUDS Web.
222 GitHub stars~648 tokensUpdated today
Auto-check passed
Diagnose Errors
Orange-OpenSource/Orange-Boosted-Bootstrap
Diagnostic workflow for build, lint, CI, and test errors in OUDS Web.
222 GitHub stars~680 tokensUpdated today
Auto-check passed

Questions about Validate Tokens

What does Validate Tokens do?

Read-only audit of OUDS design token usage across SCSS component files. Validate Tokens is an agent skill from Orange-OpenSource/Orange-Boosted-Bootstrap. Read-only audit of OUDS design token usage across SCSS component files.

When should I use Validate Tokens?

Validate Tokens fits situations like: the user asks to validate; reviewing PRs that touch scss/.scss; before a release.

How do I install Validate Tokens in Claude Code?

Run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill validate-tokens -a claude-code`. Or copy the skill folder (.github/skills/validate-tokens in Orange-OpenSource/Orange-Boosted-Bootstrap) into .claude/skills/validate-tokens in your project. Claude Code loads it when a task matches its description.

How do I install Validate Tokens in Codex?

Run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill validate-tokens -a codex`. Or copy the skill folder (.github/skills/validate-tokens in Orange-OpenSource/Orange-Boosted-Bootstrap) into .agents/skills/validate-tokens in your project. Codex loads it when a task matches its description.

Can I use Validate Tokens in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Orange-OpenSource/Orange-Boosted-Bootstrap --skill validate-tokens -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validate-tokens, .gemini/skills/validate-tokens, .github/skills/validate-tokens and .opencode/skills/validate-tokens in your project.

What does Validate Tokens need to run?

SKILL.md names no scripts, command-line tools or credentials: Validate Tokens is instructions for the agent only.

Does Validate Tokens access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Validate Tokens safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Validate Tokens use?

Validate Tokens is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Validate Tokens use?

About 620 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Validate Tokens?

Skills that share tags, products or a category with Validate Tokens: MCP Development (coollabsio/coolify, 63k stars), Transitions Polish (Jakubantalik/transitions.dev, 4.6k stars), Web Style Extractor (Lucent-Snow/style-extractor, 453 stars) and Liuguang Banlan UI (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Validate Tokens?

Orange-OpenSource (a GitHub organization) maintains it in Orange-OpenSource/Orange-Boosted-Bootstrap, which has 222 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

Source: Orange-OpenSource/Orange-Boosted-Bootstrap on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Validate Tokens

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Workflow: Validate Token Usage

Step 1 — Load brand tokens

Step 2 — Identify component SCSS files

Step 3 — For each file

Cross-brand check

Anti-pattern detection

Step 4 — Generate report

Files

Compare with similar skills

Similar skills

More from Orange-OpenSource/Orange-Boosted-Bootstrap

Related

Questions about Validate Tokens