json-configuration-management

json-configuration-management is a skill for Claude Code, Codex from cxcscmu/SkillLearnBench. It costs 15 tokens per session (176 once invoked), scanned A, original, MIT.

A fixed JSON structure for storing branding details such as colour codes and a font name. JSON is a text format commonly used to store structured settings.

In plain words
What is it for?
Use it to define colour and typography tokens, check their format, and keep brand settings in a flat configuration file.
Why use it?
It keeps branding metadata consistent and easier for tools to read and validate across engineering documents.

Skill for Claude CodeCodex

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 skills/cxcscmu/skilllearnbench/json-configuration-management
Any agent
npx skills add cxcscmu/SkillLearnBench --skill json-configuration-management
Clone the repo
git clone --depth 1 https://github.com/cxcscmu/SkillLearnBench

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 json-configuration-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/cxcscmu/skilllearnbench/json-configuration-management.svg)](https://agentmods.dev/skills/cxcscmu/skilllearnbench/json-configuration-management)
Your own site
<a href="https://agentmods.dev/skills/cxcscmu/skilllearnbench/json-configuration-management"><img src="https://agentmods.dev/badge/skills/cxcscmu/skilllearnbench/json-configuration-management.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 176 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 $0.00015 $0.00176
Opus 5 $0.00008 $0.00088
Sonnet 5 $0.00003 $0.00035
Haiku 4.5 $0.00002 $0.00018

Measured yesterday against content hash 0ab7d306ef7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

json-configuration-management 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 yesterday.

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.

skills/b1-one-shot-gemini-3.1-flash-lite-preview/anthropic-poster-design/json-configuration-management/SKILL.md · 25 lines

What it actually says

Standard JSON Schema for Branding Metadata

When defining brand assets, use the following structure to ensure consistency across the engineering handbook.

{
  "background_hex": "e6e6e6",
  "corporate_dark_hex": "1a1a1a",
  "primary_accent_hex": "007acc",
  "secondary_accent_hex": "555555",
  "tertiary_accent_hex": "aaaaaa",
  "muted_mid_gray_hex": "888888",
  "applied_heading_font": "Inter"
}

Best Practices

  • Always use 6-character hex strings.
  • Validate property names against the project-specific schema requirements before writing the file.
  • Keep the configuration flat to ensure easy parsing.
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. yesterday First seen · 25 lines · 15 tokens per session scan A 0ab7d306ef7c

Subscribe to this mod's changes

json-configuration-management is a skill published in the GitHub repository cxcscmu/SkillLearnBench (82 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 176 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-09-03.

Related

Other skills, from other repositories