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/alexmond/alexmskills/configgit clone --depth 1 https://github.com/alexmond/alexmskillsWrote 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/alexmond/alexmskills/config)<a href="https://agentmods.dev/commands/alexmond/alexmskills/config"><img src="https://agentmods.dev/badge/commands/alexmond/alexmskills/config.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.1 | $0.00020 | $0.01918 |
| Opus 5 | $0.00010 | $0.00959 |
| Sonnet 5 | $0.00004 | $0.00384 |
| Haiku 4.5 | $0.00002 | $0.00192 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 102 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
-
Locate the config script. It's shipped in the plugin cache:
ls ~/.claude/plugins/cache/alexmskills/prompt-coach/*/scripts/config.py 2>/dev/null | tail -1If not present, fall back to the source path if the user is in a dev checkout:
~/IdeaProjects/alexmskills/plugins/prompt-coach/scripts/config.py. -
Parse the user's input after
/prompt-coach:config:Direct verbs (run the script and render its output):
<empty>orshow→ runpython3 <path> showin the current cwdshow <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 toglobalunless 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> diffexport→python3 <path> exportmastery→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--opento open the URL(s) in a browser)paths→python3 <path> paths(the skill's own folders, state files, and runnable scripts; add--opento open the folder + docs in a file browser)analyze "<text>"→python3 <path> analyze "<text>"(run the FULL 42-rule catalog against one prompt) — oranalyze --last Nfor the last N logged prompts. Prefer/prompt-coach:analyzefor the coached narrative.
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.
- 5d ago First seen · 102 lines · 20 tokens per session scan A 5f327ad8dc1b
config is a command published in the GitHub repository alexmond/alexmskills (6 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,918 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.