Borrowing it
Nothing to install: this file belongs to yogasw/wick. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yogasw/wick/master/.claude/skills/config-tags/SKILL.mdgit clone --depth 1 https://github.com/yogasw/wickWrote 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.
[](https://agentmods.dev/skills/yogasw/wick/config-tags)<a href="https://agentmods.dev/skills/yogasw/wick/config-tags"><img src="https://agentmods.dev/badge/skills/yogasw/wick/config-tags.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02995 |
| Opus 5 | $0.00000 | $0.01497 |
| Sonnet 5 | $0.00000 | $0.00599 |
| Haiku 4.5 | $0.00000 | $0.00299 |
Grade A, and why
config-tags 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Tag Reference
Every exported field in a Config / Configs struct that carries a wick:"..." tag becomes one editable row in the configs table at boot time, scoped to that module's key. Fields without a tag are ignored.
Tag grammar
Tags are semicolon-separated. A key=value pair sets a named attribute; a bare key is a boolean flag.
Never put a
;insidedesc=prose. The separator is applied before anything looks at which key it is, so a semicolon in the description text ends the description there — the rest of your sentence silently disappears from the admin UI and from the connector schema the model reads. Nothing errors, and the tag still looks fine in the source. Worse, if the leftover fragment happens to read like an option (checkbox=true/false,date="YYYY-MM-DD") it is parsed as that option and switches on a widget you never asked for. Use a comma instead.TestWickTagDescriptionsAreNotSplitByProseinpkg/entityfails the build on a new one, naming the file, the line, and the text that would be dropped.
type Config struct {
// text input + description
Title string `wick:"desc=Card title shown in the UI."`
// url widget + required + description
Endpoint string `wick:"url;required;desc=API base URL. Example: https://api.example.com"`
// dropdown with fixed options
Mode string `wick:"desc=Conversion mode.;dropdown=uppercase|lowercase|titlecase"`
// multi-line textarea
Template string `wick:"desc=Prompt template.;textarea"`
// number input (also auto-applied for int/float fields)
MaxRows int `wick:"desc=Max rows returned per query.;required"`
// secret/password field
APIKey string `wick:"desc=External API key.;secret;required"`
// native checkbox (auto-applied for bool fields)
EnableCache bool `wick:"desc=Cache results across requests."`
// toggle switch — clearer on/off visual; opt-in via `bool` flag
DebugMode bool `wick:"bool;desc=Verbose logging."`
// editable table — see kvlist section below
Groups string `wick:"kvlist=id|name;desc=Visible group definitions."`
// override the auto snake_case column name
LegacyKey string `wick:"key=legacy_api_key;secret;desc=Deprecated. Kept for v1 clients."`
}
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.
- 3d ago Changed · +2 lines 7eb876de2b6b
- 7d ago First seen · 170 lines · 0 tokens per session scan A 6aea30b2752d
config-tags is a skill published in the GitHub repository yogasw/wick (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,995 tokens. 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.
Other skills, from other repositories
goai
GoAI is a Go SDK for AI applications. One unified API across 25+ LLM providers. Inspired by the Vercel AI SDK, adapted to Go idioms (generics, interfaces, channels).
wasm
WebAssembly (WASM) integration, WASI, component model, Rust/Go to WASM compilation. Use when implementing WASM modules, browser/edge compute, or polyglot runtime.
go-ops
Go development patterns, concurrency, error handling, testing, and project structure. Use for: golang, go, goroutine, channel, context, errgroup, go test, go mod, go build, interface, generics, table-driven tests, worker pool, sync.Mutex, sync.WaitGroup, pprof, go vet, golangci-lint, go workspace, functional options…
building-glamorous-tuis
Build terminal UIs with Charmbracelet (Bubble Tea, Lip Gloss, Gum). Use when: Go TUI, shell prompts/spinners, "make CLI prettier", adaptive layouts, async rendering, focus state machines, sparklines, heatmaps, kanban boards, SSH apps.
code-review-go
Deep Go-specific code review covering goroutine lifecycle, data races, error wrapping, domain modeling, and interface design. Applied in addition to the generic code-review skill when Go code is detected. Invoked when reviewing Go PRs, Go code changes, or performing Go-specific quality checks.
go-code-review
Use when reviewing Go code for performance, concurrency safety, security vulnerabilities, or readability issues.