agentmods.dev

theme-contribute

theme-contribute is a skill for Claude Code from livlign/ccthemes. It costs 47 tokens per session (565 once invoked), scanned A, original, MIT.

A workflow for submitting a custom Claude Code color theme to the ccthemes gallery on GitHub.

In plain words
What is it for?
Use it to validate a theme, add it to the gallery, and open a pull request for other developers to use.
Why use it?
It checks the theme's format, color values, readability, and filename before proposing the change, reducing avoidable review problems.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the theme-gallery plugin — 2 skills shipped together

not rated 2repo 1mo ago A scan 47 tokens original MIT

Good fit Use it to validate a theme, add it to the gallery, and open a pull request for other developers to use.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/livlign/ccthemes/theme-contribute
View source ↗ livlign/ccthemes
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 livlign/ccthemes --skill theme-contribute
Clone the repo
git clone --depth 1 https://github.com/livlign/ccthemes

Made for: Claude Code.

Or install theme-gallery, the plugin that ships this one along with the rest of its 2 skills.

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 theme-contribute

README.md
[![agentmods](https://agentmods.dev/badge/skills/livlign/ccthemes/theme-contribute.svg)](https://agentmods.dev/skills/livlign/ccthemes/theme-contribute)
Your own site
<a href="https://agentmods.dev/skills/livlign/ccthemes/theme-contribute"><img src="https://agentmods.dev/badge/skills/livlign/ccthemes/theme-contribute.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 565 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.00047 $0.00565
Opus 5 $0.00023 $0.00282
Sonnet 5 $0.00009 $0.00113
Haiku 4.5 $0.00005 $0.00056

Measured 7d ago against content hash 8cd19a1baeeb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

theme-contribute 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 7d 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/theme-gallery/skills/theme-contribute/SKILL.md · 41 lines

What it actually says

Take one of the user's custom themes and open a PR adding it to the ccthemes catalog at github.com/livlign/ccthemes (themes live in plugins/theme-gallery/themes/).

Steps

  1. Pick the theme. If the user didn't name one, list ~/.claude/themes/*.json and ask which to contribute. Read the file.

  2. Validate it before proposing a PR — fail loudly, don't silently "fix":

    • name (string) and base present; base is one of dark, light, dark-daltonized, light-daltonized, dark-ansi, light-ansi.
    • overrides is an object; every value is a valid color (#rrggbb / #rgb / rgb(r,g,b) / ansi256(n) / ansi:<name>).
    • Warn on unknown token names (Claude Code ignores them, but they usually mean a typo).
    • Sanity-check legibility: on a dark base, diffAdded/diffRemoved should be dark tints (not near-white); on light, pale tints. Flag anything that looks like a vivid foreground color used as a diff background.
    • Choose a kebab-case slug for the filename; make sure it doesn't collide with an existing file in the catalog.

  3. Open the PR with gh:

    • Fork/clone livlign/ccthemes if the user doesn't have it (respect existing checkout).
    • Add the file at plugins/theme-gallery/themes/<slug>.json.
    • Branch add-theme/<slug>, commit feat: add <name> theme, push, and gh pr create with a body that names the theme, its base, and a one-line description of the look. Link the PR back to the user.

  4. Never commit secrets or the user's unrelated settings — only the single theme JSON.

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. 7d ago First seen · 41 lines · 47 tokens per session scan A 8cd19a1baeeb

Subscribe to this mod's changes

theme-contribute is a skill published in the GitHub repository livlign/ccthemes (2 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 565 once invoked, about $0.0002 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.

Claude CodeCommitsGit and workflowcatppuccinclaude-code-plugincolor-schemedark-themedracula
Related

Other skills, from other repositories

commit

Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…

ReflexioAI/claude-smart · 122 tokens

phx-pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 61 tokens

branch-and-worktree-workflow

Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…

cbrock84/headcount · 70 tokens

precommit

Pre-commit checks — lint:fix -> build -> test.

sd0xdev/sd0x-harness · 15 tokens

next-step

Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.

sd0xdev/sd0x-harness · 63 tokens

precommit-fast

Quick pre-commit checks — lint:fix -> test.

sd0xdev/sd0x-harness · 15 tokens