wick: Skill for Claude Code

.claude/skills/encrypted-fields/SKILL.md

encrypted-fields is a skill for Claude Code from yogasw/wick. It costs 85 tokens per session (2,072 once invoked), scanned A, original, MIT.

Instructions for handling credentials, tokens, and other sensitive values in connectors. It explains how to encrypt these values so they can move between calls without appearing as readable text to the agent or in logs.

In plain words
What is it for?
Adding or reviewing connector fields that contain credentials, masking sensitive response data, and passing encrypted values safely between operations.
Why use it?
It reduces the risk of exposing passwords, API keys, session tokens, and similar secrets during connector use.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is yogasw/wick's own configuration. It tells Claude Code how to work on wick itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything wick configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/yogasw/wick/master/.claude/skills/encrypted-fields/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/yogasw/wick

Made for: Claude Code.

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 encrypted-fields

README.md
[![agentmods](https://agentmods.dev/badge/skills/yogasw/wick/encrypted-fields/github.svg)](https://agentmods.dev/skills/yogasw/wick/encrypted-fields)
Your own site
<a href="https://agentmods.dev/skills/yogasw/wick/encrypted-fields"><img src="https://agentmods.dev/badge/skills/yogasw/wick/encrypted-fields/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for encrypted-fields

Your own site · 80×15
<a href="https://agentmods.dev/skills/yogasw/wick/encrypted-fields"><img src="https://agentmods.dev/badge/skills/yogasw/wick/encrypted-fields.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,072 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.00085 $0.02072
Opus 5.5 $0.00034 $0.00829
Sonnet 5.5 $0.00017 $0.00414
Haiku 4.5 $0.00009 $0.00207

Measured 2mo ago against content hash 01ae2c0f19ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

encrypted-fields 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 2mo 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.

.claude/skills/encrypted-fields/SKILL.md · 139 lines

How it starts

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

Encrypted Fields

Wick has a built-in encrypted-fields layer that lets credentials flow between an LLM and a connector without ever appearing as plaintext in the LLM's context window or in the audit log. Treat this as the default for any sensitive value.

When this skill activates

  • Adding a new connector that takes a credential, API key, or token (Configs field).
  • Adding an operation whose response includes a credential, OTP, session token, JWT, refresh token, or any value the LLM should pass forward but not learn.
  • Reviewing an existing connector for plaintext-leak risk.
  • The user mentions wick_enc_, "encrypt this value", "hide this from the LLM", or asks why a credential is showing up unmasked.
  • Adding a sensitive Input field that the LLM may receive in a previous response and replay in a later call.

If the work has nothing to do with credentials or sensitive output, skip this skill.

How the layer works (in 30 seconds)

  1. Tag the field secret in the Configs / Input struct.
  2. connectors.Service.Execute automatically:
    • decrypts any wick_enc_<...> token in the input map (and the stored configs map) before calling ExecuteFunc, so your code only ever sees plaintext.
    • masks every occurrence of those plaintext values in the marshaled response with wick_enc_<token>, so the LLM never sees plaintext.
  3. The audit log stores wick_enc_ (pre-decrypt) in request_json and wick_enc_ (post-encrypt) in response_json. Retry from history works because Execute re-decrypts under the retrier's key.
  4. Keys are per-user — HKDF(master_key, salt=user_uuid, info="wick-enc"). A token issued for user A cannot be decrypted under user B's session.

The token format is wick_enc_<base64url(nonce ‖ AES-256-GCM(plaintext, nonce, derived_key))>. AES-256-GCM, 12-byte random nonce per encrypt, 32-byte derived key.

Recipes

Recipe 1: a Configs credential (most common)

type Creds struct {
    Endpoint string `wick:"required"`
    APIKey   string `wick:"required;secret"` // ← auto-masked in every response
}

Read the full file on GitHub · 139 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. 2mo ago First seen · 139 lines · 85 tokens per session scan A 01ae2c0f19ac

Subscribe to this mod's changes

encrypted-fields is a skill published in the GitHub repository yogasw/wick (3 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 2,072 once invoked, about $0.0003 per session on Opus 5.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.

Related

Other skills, from other repositories

n8n

Use when the user wants to build, debug, or extend an n8n workflow - generating workflow JSON from a description, scaffolding a custom TypeScript node, building an AI agent (LangChain cluster), iterating over items, writing Code-node JS, linting an existing workflow, diagnosing a failed execution, or driving a live…

AutomateLab-tech/n8n-mcp · 78 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

redteam-web-detail-pack

Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.

Netw0rkNoob/VulnClaw · 38 tokens

android-pentest

A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.

Netw0rkNoob/VulnClaw · 32 tokens

workflow-builder

Load before calling workflowbuilderbuildworkflow. Use for single-workflow work: new one-off workflows, existing-workflow edits, verification repairs, and workflow-local data tables. For any other new workflow, load intent-recognition first when it is listed. Write or edit a workspace source file, then call…

n8n-io/n8n · 213 tokens

no-code-app

Use when building an app on a no-code/low-code platform (Bubble, Softr, Glide over Airtable or Xano) — picking the platform, modeling the data, keeping usage-metered cost predictable, and planning the exit before lock-in. NOT a hand-written coded app (that is nextjs), NOT wiring SaaS tools together with no app UI…

ericrisco/rsc-harness · 87 tokens