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.
npx agentmods add commands/albertnahas/claude-core-values/core-valuesgit clone --depth 1 https://github.com/albertnahas/claude-core-valuesWrote 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/commands/albertnahas/claude-core-values/core-values)<a href="https://agentmods.dev/commands/albertnahas/claude-core-values/core-values"><img src="https://agentmods.dev/badge/commands/albertnahas/claude-core-values/core-values.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 | $0.00010 | $0.00503 |
| Opus 5 | $0.00005 | $0.00251 |
| Sonnet 5 | $0.00002 | $0.00101 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
core-values 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.
What it actually says
Manage the user's core development values configuration.
Determine Action
Check the user's argument:
- No argument or "show": Display current values
- "init": Initialize or reinitialize values from a template
Show Current Values
- Look for the config file in this order:
- Project-level:
<current working directory>/.claude/core-values.yml - User-level:
~/.claude/core-values.yml
- Project-level:
- If found, read the file and display the values in a nicely formatted summary
- If not found, tell the user no core values are configured and offer to run
/core-values init
Initialize Values
- Read all template files from
$CLAUDE_PLUGIN_ROOT/templates/using Glob for$CLAUDE_PLUGIN_ROOT/templates/*.yml, then Read each file - Present the available templates to the user using AskUserQuestion with these options:
- Craftsman — Quality-obsessed. No half solutions. No shortcuts. Zero tolerance for broken code.
- Startup — Ship fast, iterate rapidly, pragmatic quality. Bias for action.
- Security-First — Defense in depth, zero trust, OWASP compliance. Security as foundation.
- Minimal — Simple baseline: working code, follow patterns, test before push.
- After the user picks a template, read the chosen template YAML from
$CLAUDE_PLUGIN_ROOT/templates/<name>.yml - Ask the user where to install using AskUserQuestion:
- User-level (~/.claude/core-values.yml) — Applies to all projects (Recommended)
- Project-level (.claude/core-values.yml) — Only this project
- Create the
.claude/directory if it doesn't exist, then write the template content to the chosen path - Tell the user:
- Their values are now active and will load on every new session
- They can edit the YAML file directly to customize sections, add values, or change the motto
- Project-level config takes precedence over user-level if both exist
- Restart Claude Code (or start a new session) for values to take effect
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 First seen · 42 lines · 10 tokens per session scan A 76f5f9cb7d3a
core-values is a command published in the GitHub repository albertnahas/claude-core-values (5 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 503 once invoked, about $0.0001 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.