config-orchestration

config-orchestration is a skill for Claude Code from LiorCohen/sdd. It costs 22 tokens per session (1,040 once invoked), scanned A, original, no licence file.

A coordinator for project configuration tasks, including generating, checking, comparing, and adding environment variables.

In plain words
What is it for?
Use it to generate configuration, validate it, compare versions, and add environment-specific variables.
Why use it?
It helps keep configuration changes consistent and makes differences or invalid settings easier to find.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the sdd plugin — 47 skills, 3 commands, 7 agents shipped together

Good fit Use it to generate configuration, validate it, compare versions, and add environment-specific variables.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/liorcohen/sdd/config-orchestration
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.

Any agent
npx skills add LiorCohen/sdd --skill config-orchestration
Clone the repo
git clone --depth 1 https://github.com/LiorCohen/sdd

Made for: Claude Code.

Or install sdd, the plugin that ships this one along with the rest of its 47 skills, 3 commands, 7 agents.

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-orchestration

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/liorcohen/sdd/config-orchestration"><img src="https://agentmods.dev/badge/skills/liorcohen/sdd/config-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,040 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 unknown 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.00022 $0.01040
Opus 5 $0.00011 $0.00520
Sonnet 5 $0.00004 $0.00208
Haiku 4.5 $0.00002 $0.00104

Measured 6d ago against content hash 01947f7db18e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

config-orchestration 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 6d 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.

plugin/fullstack-typescript/skills/orchestrators/config-orchestration/SKILL.md · 166 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 6d ago First seen · 166 lines · 22 tokens per session scan A 01947f7db18e

Subscribe to this mod's changes

config-orchestration is a skill published in the GitHub repository LiorCohen/sdd (43 stars, last pushed 6mo ago), with no licence file. It adds 22 tokens to every session and 1,040 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-09-03.

Related

Other skills, from other repositories

scaffold

Bootstrap a new project with your stack, auth, database, and standards pre-configured.

vikisingh23/neuraforge-ai · 20 tokens

work-beads

Work the project's Beads task queue end-to-end - claim a bead, build in an isolated worktree, verify, review, merge, close, report. Use when the user says "/work-beads", "/work-beads 5", "work the next N beads", "work on ", "pick up some open tasks", or asks to work the backlog. Applies to every coding agent (Claude…

zigrivers/scaffold · 106 tokens

work

Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it, or a sentence of editorial direction as a rider. Use when asked to work a ticket end-to-end.

mikestankavich/claude-ship-workflow · 0 tokens

batch

Dispatch a night's batch of Todo tickets — one worktree and one pull request each — and leave a morning summary. Run explicitly; never inferred.

mikestankavich/claude-ship-workflow · 31 tokens

prep

Spec a ticket before it is dispatched. Brainstorms it, decides everything it can recommend an answer for, asks a present human about the little that survives, and leaves the spec, the decisions and anything still open as one ticket comment. No worktree, no branch, no pull request, and the ticket stays where it was.

mikestankavich/claude-ship-workflow · 0 tokens

fleet

The single-pane session roster (/foundry:fleet) — every active Claude Code session joined to its foundry work-context (epic/atom/governance), over the NATIVE session list. Read-only/advisory. Trigger to see all your parallel sessions at a glance with their foundry context, or when supervising many sessions and asking…

lukasrepublic/agentic-foundry · 83 tokens