preferences

preferences is a skill for Claude Code from AxGord/claude-workflow. It costs 7 tokens per session (1,327 once invoked), scanned A, original, MIT.

A collection of the user's general coding preferences and rules for how code should be written. It also describes how project lint settings take priority for machine-checkable style rules.

In plain words
What is it for?
Use it when writing or reviewing code, especially for field initialization, immutability, naming, visibility, magic numbers, exception handling, and project lint configuration.
Why use it?
It helps keep generated code consistent with the user's preferences and avoids silently guessing when the required lint rules are unavailable.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; mentions subagents; names the AskUserQuestion tool.

Part of the workflow plugin — 28 skills, 2 hooks, 1 MCP server shipped together

Good fit Use it when writing or reviewing code, especially for field initialization, immutability…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/axgord/claude-workflow/preferences
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 AxGord/claude-workflow --skill preferences
Clone the repo
git clone --depth 1 https://github.com/AxGord/claude-workflow

Made for: Claude Code.

Or install workflow, the plugin that ships this one along with the rest of its 28 skills, 2 hooks, 1 MCP server.

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 preferences

README.md
[![agentmods](https://agentmods.dev/badge/skills/axgord/claude-workflow/preferences.svg)](https://agentmods.dev/skills/axgord/claude-workflow/preferences)
Your own site
<a href="https://agentmods.dev/skills/axgord/claude-workflow/preferences"><img src="https://agentmods.dev/badge/skills/axgord/claude-workflow/preferences.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,327 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.00007 $0.01327
Opus 5 $0.00003 $0.00664
Sonnet 5 $0.00001 $0.00265
Haiku 4.5 $0.00001 $0.00133

Measured 6d ago against content hash 05b3657dc7f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

preferences 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 6d 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.

templates/skills/preferences/SKILL.md · 99 lines

How it starts

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

User's personal coding preferences

These rules are set by the user through direct feedback. They ALWAYS take priority over base skills.

Model usage

  • Use Opus or Sonnet for subagents
  • Never use Haiku — quality too low for real work

Linter-owned defaults

The machine-checkable preferences (immutability, member order, explicit visibility, _-prefix naming, magic numbers, ternary returns, no swallowed exceptions, dead-weight removal) live as compilable lists in the user's preferences-lint skill and are compiled into each project's lint config by lint-setup. The PROJECT's lint config is authoritative — write to satisfy it; the linter is the correction net. In a project with no lint config (and where lint-setup is not installed), load preferences-lint deliberately if the machine-checkable details are needed; if preferences-lint is ALSO unavailable on this machine, these categories have no substitute text — say so in the report instead of silently proceeding without them.

Field initialization

  • Initialize fields at the declaration site when the value does NOT depend on constructor parameters
  • Only assign in the constructor when the value requires constructor args or complex logic
  • This applies to all languages: final _bg:Sprite = new Sprite(), readonly List<int> _items = new(), etc.

Naming

  • Event listener methods: use Handler suffix, not on prefix — e.g. frameSelectHandler, not onFrameSelect

Comments and documentation

  • All code comments and documentation must be in English only — no other languages in source code
  • Empty line before a doc comment (/** */) on a field — visually separates documented members
  • Comment only when behavior is non-obvious from the code. Don't paraphrase the line above; don't restate what the type/name already says

Formatting

  • No curly braces {} for single-line bodies (if, for, function, etc.) — reduces visual noise
  • Combine for + if into for (...) if (...) { — preferred over if (!cond) continue; inside loop body. Guard reads naturally, continue inverts the condition and wastes a line

Read the full file on GitHub · 99 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. 6d ago First seen · 99 lines · 7 tokens per session scan A 05b3657dc7f8

Subscribe to this mod's changes

preferences is a skill published in the GitHub repository AxGord/claude-workflow (5 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 1,327 once invoked, about $0.0000 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens