Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add scolladon/craft/plugin install craftWrote 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/scolladon/craft/promote-config)<a href="https://agentmods.dev/skills/scolladon/craft/promote-config"><img src="https://agentmods.dev/badge/skills/scolladon/craft/promote-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.
<a href="https://agentmods.dev/skills/scolladon/craft/promote-config"><img src="https://agentmods.dev/badge/skills/scolladon/craft/promote-config.svg" alt="Reviewed on agentmods" width="80" 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.00085 | $0.01285 |
| Opus 5 | $0.00043 | $0.00642 |
| Sonnet 5 | $0.00017 | $0.00257 |
| Haiku 4.5 | $0.00009 | $0.00128 |
Grade A, and why
promote-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 9d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
craft:promote-config — relocate a named config between scopes
Standalone, session-owned skill. You (the session) ask the plan computer where the config should go, stage the source bytes at that destination, land through the existing lint-then-move bin, and finalize by removing the source. No worker agent is spawned.
Input: $ARGUMENTS — <name> (required), plus optional --demote and --force.
This is a MOVE by default: the source is removed once the destination copy lands clean, so the config lives at exactly one scope afterward, never both.
Preamble — plugin-root probe (read-only)
Confirm both entrypoints this skill composes exist:
test -f "${CRAFT_ROOT:-${CLAUDE_PLUGIN_ROOT}}/engine/bin/promote-plan.js"
test -f "${CRAFT_ROOT:-${CLAUDE_PLUGIN_ROOT}}/engine/bin/init-land.js"
If either test fails, surface a diagnostic and stop — the plugin installation is incomplete.
Parse $ARGUMENTS:
<name>— required. Absent ⇒ STOP: "a config name is required".--demote— direction flag. Absent ⇒ promote (local→user, the default). Present ⇒ demote (user→local).--force— overwrite flag, forwarded verbatim when the caller supplied it.
Procedure
Step 1 — Plan
Every decision — direction, source-existence, destination-exists refuse-vs-force,
and $HOME-containment — is made by promote-plan.js, never re-derived here:
plan_out="$(node "${CRAFT_ROOT:-${CLAUDE_PLUGIN_ROOT}}/engine/bin/promote-plan.js" "$name" [--demote] [--force])"
(append --demote and/or --force only when the caller passed them).
Non-zero exit ⇒ STOP — surface the stderr diagnostic verbatim (no source config to
relocate, a destination that already exists without --force, a $HOME
containment escape, or an invalid name). Nothing is touched.
On exit 0, parse the three key=value lines from $plan_out:
source=<absolute source path>
dest=<absolute destination path>
scope=<user|local — the destination scope>
Bind source, dest, scope from these lines.
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.
- 9d ago First seen · 138 lines · 85 tokens per session scan A 27db5ddee795
promote-config is a skill published in the GitHub repository scolladon/craft (2 stars, last pushed 21d ago), licensed MIT. It adds 85 tokens to every session and 1,285 once invoked, about $0.0004 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
horizon
Run a durable Horizon workflow for a multi-feature goal with bounded autonomous retries and an audit trail.
check-in
Record a Parallax protocol checkpoint with concrete evidence before gated implementation work.
debug
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
hyperplan
Harden a non-trivial plan through a three-round adversarial critique and evidence-based synthesis.
parallax
Compatibility entry point for the Parallax workflow when Claude resolves it as a plugin skill.
plan
Create an execution-ready Parallax plan grounded in repository evidence and explicit verification.