add-config

add-config is a skill for Claude Code, Codex from mits-pl/wove. It costs 37 tokens per session (3,452 once invoked), scanned A, original, Apache-2.0.

A guide to adding user-configurable settings to Wave Terminal’s configuration system, including defaults, validation, and documentation.

In plain words
What is it for?
Use it to introduce a configuration key, set its default, validate it, support overrides, and document it for users.
Why use it?
It identifies every place a new setting must be added and explains how settings flow from defaults to user and block-specific overrides.

Skill for Claude CodeCodex

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

Good fit Use it to introduce a configuration key, set its default, validate it, support overrides, and document it for users.

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

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 add-config

README.md
[![agentmods](https://agentmods.dev/badge/skills/mits-pl/wove/add-config.svg)](https://agentmods.dev/skills/mits-pl/wove/add-config)
Your own site
<a href="https://agentmods.dev/skills/mits-pl/wove/add-config"><img src="https://agentmods.dev/badge/skills/mits-pl/wove/add-config.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,452 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.00037 $0.03452
Opus 5 $0.00018 $0.01726
Sonnet 5 $0.00007 $0.00690
Haiku 4.5 $0.00004 $0.00345

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

Security

Grade A, and why

add-config 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 8d 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.

.kilocode/skills/add-config/SKILL.md · 472 lines

How it starts

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

Adding a New Configuration Setting to Wave Terminal

This guide explains how to add a new configuration setting to Wave Terminal's hierarchical configuration system.

Configuration System Overview

Wave Terminal uses a hierarchical configuration system with:

  1. Go Struct Definitions - Type-safe configuration structure in pkg/wconfig/settingsconfig.go
  2. JSON Schema - Auto-generated validation schema in schema/settings.json
  3. Default Values - Built-in defaults in pkg/wconfig/defaultconfig/settings.json
  4. User Configuration - User overrides in ~/.config/waveterm/settings.json
  5. Block Metadata - Block-level overrides in pkg/waveobj/wtypemeta.go
  6. Documentation - User-facing docs in docs/docs/config.mdx

Settings cascade from defaults → user settings → connection config → block overrides.

Step-by-Step Guide

Step 1: Add to Go Struct Definition

Edit pkg/wconfig/settingsconfig.go and add your new field to the SettingsType struct:

type SettingsType struct {
    // ... existing fields ...

    // Add your new field with appropriate JSON tag
    MyNewSetting string `json:"mynew:setting,omitempty"`

    // For different types:
    MyBoolSetting   bool    `json:"mynew:boolsetting,omitempty"`
    MyNumberSetting float64 `json:"mynew:numbersetting,omitempty"`
    MyIntSetting    *int64  `json:"mynew:intsetting,omitempty"`    // Use pointer for optional ints
    MyArraySetting  []string `json:"mynew:arraysetting,omitempty"`
}

Naming Conventions:

  • Use namespace prefixes (e.g., term:, window:, ai:, web:, app:)
  • Use lowercase with colons as separators
  • Field names should be descriptive and follow Go naming conventions
  • Use omitempty tag to exclude empty values from JSON

Type Guidelines:

  • Use *int64 and *float64 for optional numeric values
  • Use *bool for optional boolean values (or bool if default is false)
  • Use string for text values
  • Use []string for arrays
  • Use float64 for numbers that can be decimals

Read the full file on GitHub · 472 lines

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. 8d ago First seen · 472 lines · 37 tokens per session scan A 51ec9ebc84e2

Subscribe to this mod's changes

add-config is a skill published in the GitHub repository mits-pl/wove (42 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 3,452 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-30.

Related

Other skills, from other repositories

build-teaql-app

Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…

teaql/teaql-agent-kit · 112 tokens

stuck

Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.

QwenLM/qwen-code · 57 tokens

desktop-brand-builder

Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop-shell.

QwenLM/qwen-code · 69 tokens

repo-hygiene

Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.

QwenLM/qwen-code · 48 tokens

coordinate

Coordinate a small team of Qwen Code teammates with enforced read-only workers, an optional worktree-pinned writer, shared tasks, peer messages, and existing Agent View tabs. Invoke explicitly with /coordinate.

QwenLM/qwen-code · 43 tokens

find-simplifications

Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…

QwenLM/qwen-code · 103 tokens