agentmods.dev

config

config is a command for Claude Code from alexmond/alexmskills. It costs 20 tokens per session (1,866 once invoked), scanned A, original, MIT.

A command-line dashboard for viewing and changing prompt-coach settings. It shows options by category and supports inspecting, setting, resetting, comparing, and exporting configuration.

In plain words
What is it for?
Use it to inspect or change settings for output, rule activation, mastery, praise, typo handling, and backup behavior.
Why use it?
It makes the coach's behavior adjustable without manually editing configuration files.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool.

Part of the prompt-coach plugin — 1 skill, 8 commands shipped together

not rated 10repo +1 changed 1mo ago A scan 20 tokens original MIT

Good fit Use it to inspect or change settings for output, rule activation, mastery, praise, typo handling, and backup behavior.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alexmond/alexmskills/config
View source ↗ alexmond/alexmskills alexmond.org
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.

Clone the repo
git clone --depth 1 https://github.com/alexmond/alexmskills

Made for: Claude Code.

Or install prompt-coach, the plugin that ships this one along with the rest of its 1 skill, 8 commands.

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 config

README.md
[![agentmods](https://agentmods.dev/badge/commands/alexmond/alexmskills/config/github.svg)](https://agentmods.dev/commands/alexmond/alexmskills/config)
Your own site
<a href="https://agentmods.dev/commands/alexmond/alexmskills/config"><img src="https://agentmods.dev/badge/commands/alexmond/alexmskills/config/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 config

Your own site · 80×15
<a href="https://agentmods.dev/commands/alexmond/alexmskills/config"><img src="https://agentmods.dev/badge/commands/alexmond/alexmskills/config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 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,866 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.00020 $0.01866
Opus 5.5 $0.00008 $0.00746
Sonnet 5.5 $0.00004 $0.00373
Haiku 4.5 $0.00002 $0.00187

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

Security

Grade A, and why

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 1mo 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.

plugins/prompt-coach/commands/config.md · 96 lines

How it starts

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

/prompt-coach:config

Structured surface for the coach's growing config catalog. Backs onto a schema of every option (category, type, default, allowed values, description, example, since-version) so new options are picked up automatically when they're added.

What to do

  1. Resolve scripts/config.py from this plugin's root (the parent of this commands/ directory). This works in either client's cache or a dev checkout.

  2. Parse the user's input after /prompt-coach:config:

    Direct verbs (run the script and render its output):

    • <empty> or show → run python3 <path> show in the current cwd
    • show <category> → python3 <path> show <category> (categories: output, rule-activation, mastery, praise, typo-tolerance, llm-fallback)
    • get <key> → python3 <path> get <key>
    • describe <key> → python3 <path> describe <key>
    • options <key> → python3 <path> options <key> (lists legal values with per-choice explanations)
    • set <key> <value> → python3 <path> set <key> <value> --scope <scope> (scope defaults to global unless the user says "in this repo" / "for this repo" → then --scope repo)
    • reset <key> → python3 <path> reset <key> --scope <scope>
    • reset-all → python3 <path> reset-all --scope <scope> (require explicit confirmation before running without --dry-run)
    • diff → python3 <path> diff
    • export → python3 <path> export
    • mastery → python3 <path> mastery (dashboard of mastered / in-progress / dormant rules)
    • mastery-reset <rule-id> → python3 <path> mastery-reset <rule-id> (dry-run once first)
    • mastery-reset-all → python3 <path> mastery-reset-all (dry-run once first, require explicit confirmation)
    • sources [<rule-id>] → python3 <path> sources [<rule-id>] (citation trail + doc URLs; add --open to open the URL(s) in a browser)
    • paths → python3 <path> paths (the skill's own folders, state files, and runnable scripts; add --open to open the folder + docs in a file browser)
    • analyze "<text>" → python3 <path> analyze "<text>" (run the FULL 42-rule catalog against one prompt) — or analyze --last N for the last N logged prompts. Prefer /prompt-coach:analyze for the coached narrative.

Read the full file on GitHub · 96 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. 1mo ago Changed · -6 lines dbf68724177b
  2. 1mo ago First seen · 102 lines · 20 tokens per session scan A 5f327ad8dc1b

Subscribe to this mod's changes

config is a command published in the GitHub repository alexmond/alexmskills (10 stars, last pushed 12d ago), licensed MIT. It adds 20 tokens to every session and 1,866 once invoked, about $0.0001 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.

Claude Codeai-agentsanthropicautomationclaudedeveloper-tools
Related

Other commands, from other repositories

deps-audit

Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.

wshobson/agents · 23 tokens

review-branch

Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.

damusix/atomic-claude · 35 tokens

discuss

A command that interviews you in five phases and saves a detailed description of a proposed feature or change. EARS is a structured way to write requirements so they can be checked clearly.

fockus/skill-memory-bank · 45 tokens

standup

Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.

skullninja/coco-workflow · 21 tokens

rev

Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.

olehsvyrydov/AI-development-team · 16 tokens

design-audit

Audit the rendered design of live sites. Evidence capture first, then one critique per site. Argument is a URL, a repo name, or all.

w2ur/claude-code-setup · 30 tokens