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 skills/nick-railsback/skill-engine/config-setnpx skills add nick-railsback/skill-engine --skill config-setgit clone --depth 1 https://github.com/nick-railsback/skill-engineWrote 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/skills/nick-railsback/skill-engine/config-set)<a href="https://agentmods.dev/skills/nick-railsback/skill-engine/config-set"><img src="https://agentmods.dev/badge/skills/nick-railsback/skill-engine/config-set.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.00035 | $0.00739 |
| Opus 5 | $0.00017 | $0.00369 |
| Sonnet 5 | $0.00007 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
config-set 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config set
Persist an engine-wide configuration value. The single key the engine reads today is diff.tool — the command /skill-engine:review prints when surfacing how to inspect a proposed-vs-live diff. The default value is git diff --no-index --color; users with a preferred diff tool override it once and the choice persists across sessions.
Argument shape
/skill-engine:config-set <key> "<value>"
Example invocations:
/skill-engine:config-set diff.tool "delta"
/skill-engine:config-set diff.tool "git diff --no-index --color"
/skill-engine:config-set diff.tool "code --diff"
The <value> is taken verbatim; quote it so shell-splitting does not eat embedded spaces. The engine does not validate that the configured command exists on the user's PATH — that is the user's responsibility. A misconfigured command surfaces as a runtime failure when /skill-engine:review prints it and the user runs it.
Resolution of the config file
The config file lives at $CLAUDE_PLUGIN_DATA/config.json. The directory is created if absent.
When $CLAUDE_PLUGIN_DATA is unset, surface:
$CLAUDE_PLUGIN_DATA is unset. The engine's plugin-data tree is not reachable from this shell. Run the skill from a Claude Code session where the plugin is installed, or set $CLAUDE_PLUGIN_DATA to the engine's plugin-data directory.
Exit non-zero. Do not write a config file to a fallback location — the engine's other surfaces (/skill-engine:review) key off $CLAUDE_PLUGIN_DATA, and writing to a different path would create a config that the readers never find.
The write
Read the existing config.json (or initialize an empty object if absent). Merge the new key/value into it, preserving any other keys present. Write back with schema_version: 1 if not already set.
Example file shape after /skill-engine:config-set diff.tool "delta":
{
"schema_version": 1,
"diff.tool": "delta"
}
The flat key shape (diff.tool as one string, not nested) keeps the file shallow and matches the argument the user typed. Future keys (diff.binary, cache.location, etc.) follow the same shape.
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 · 64 lines · 35 tokens per session scan A f48f59a1b142
config-set is a skill published in the GitHub repository nick-railsback/skill-engine (2 stars, last pushed 26d ago), licensed MIT. It adds 35 tokens to every session and 739 once invoked, about $0.0002 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 skills, from other repositories
skill-creator
Create or improve Zhin Agent skills (SKILL.md). Use when asked to add a skill, write SKILL.md, document a repeatable agent workflow, or refine skill frontmatter/keywords. Triggers: 创建技能, 写 SKILL, skill-creator, 加 skill.
skill-sync-checker
Detects content drift between skill files and their source documents. Helps maintain skills that are derived from other documentation by comparing content and flagging outdated sections.
tech-design-generation
Generates professional Technical Design Documents following industry-standard engineering practices. This skill activates when the user asks to write a technical design, create an architecture design, draft a design doc, write a technical proposal, do system design, create a technical design document, write an RFC…
test-cases-generation
Generates structured test case sets with multi-dimensional coverage from project code analysis or specification documents. This skill activates when the user asks to write test cases, generate tests, supplement tests, create test coverage, or improve test completeness. It auto-scans the project to extract testable…
erpaval
Workflow for autonomous software development with the Kiro CLI (open Agent Skills standard). Classifiers route scope, complexity, directory state, and spec readiness before committing to Explore / Research / Plan / Act / Validate, then close the loop with a Compound step that persists lessons to .erpaval/solutions/…
idea
Use when exploring a new idea before writing formal specifications. Guides users through iterative discovery, research, and critical analysis to crystallize vague ideas into validated requirement drafts. Includes anti-pseudo-requirement checks, competitive research, demand evidence gathering, and "What if we don't…