standards-config

A project command for setting and managing the configuration used by Claude development standards. It supports settings that can be tailored to a specific project.

In plain words
What is it for?
Creating, changing, and maintaining configuration values for Claude-based development work.
Why use it?
It keeps project-specific development settings in one place instead of relying on scattered or repeated instructions.

Command

Part of the claude-standards plugin — 4 commands shipped together

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 commands/wqaetly/claude-code-plugins/standards-config
Clone the repo
git clone --depth 1 https://github.com/wqaetly/claude-code-plugins

Or install claude-standards, the plugin that ships this one along with the rest of its 4 commands.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,261 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00000 $0.01261
Opus 5 $0.00000 $0.00630
Sonnet 5 $0.00000 $0.00252
Haiku 4.5 $0.00000 $0.00126

Measured 3d ago against content hash 57ce4e5fd8e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

standards-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 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.

claude-standards/commands/standards-config.md · 196 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 3d ago First seen · 196 lines · 0 tokens per session scan A 57ce4e5fd8e3

Subscribe to this mod's changes

standards-config is a command published in the GitHub repository wqaetly/claude-code-plugins (5 stars, last pushed 10mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,261 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.