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 skills add soulcodex/agentic --skill deploy-configgit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/deploy-config)<a href="https://agentmods.dev/skills/soulcodex/agentic/deploy-config"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/deploy-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/soulcodex/agentic/deploy-config"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/deploy-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.00582 |
| Opus 5.5 | $0.00026 | $0.00233 |
| Sonnet 5.5 | $0.00013 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
deploy-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.
What it actually says
Deploy Config Skill
Deploy the complete agentic configuration to a target project.
Step 1 — Confirm Target and Profile
Ask the user:
- Target project path (absolute or relative)
- Profile name (run
just list-profilesif unsure) - Skills to deploy (run
just list-skillsif unsure; can be "all" or a comma-separated list) - Which vendors to generate files for
Step 2 — Check for Existing Config
Read {target}/.agentic/config.yaml if it exists.
If it does, show the current profile and version, and ask if the user wants to update or replace.
Step 3 — Run the Full Deploy Pipeline
# 1. Compose AGENTS.md from the profile
just compose {profile} {target}
# 2. Generate vendor-specific files
just vendor-gen {target} --vendors {vendors}
# 3. Deploy selected skills
just deploy-skills {target} --skills {skills}
Step 4 — Verify Output
After deploying, list the files created in the target project:
AGENTS.md— primary agent instructionsCLAUDE.md— Claude adapter (if claude vendor enabled).github/copilot-instructions.md— Copilot adapter (if copilot enabled)GEMINI.md— Gemini primary context file (auto-discovered, if gemini enabled).gemini/system.md— Gemini system-prompt override (requiresGEMINI_SYSTEM_MD=1, if gemini enabled).gemini/skills/— Gemini skills directory (symlinked, if gemini enabled).claude/skills/*/— deployed skill directories (if claude enabled).agentic/config.yaml— lock file recording what was deployed
Step 5 — Next Steps
Suggest to the user:
- Commit the generated files to the target project
- Run
just validate {target}to verify the config is valid - Run
just sync-check {target}periodically to detect drift from the library
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.
- 1mo ago First seen · 69 lines · 64 tokens per session scan A 1856f4f0f469
deploy-config is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 582 once invoked, about $0.0003 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.
Other skills, from other repositories
skill-navigator
A skill that recommends which already-installed local agent skill matches a described task. It uses the machine's skill catalogue and does not perform the task itself.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
opencli-usage
Discover and invoke OpenCLI capabilities for websites and Chrome. Find commands, inspect schemas, interpret results and choose browser or adapter tools.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
pinme-llm
Use this skill when a PinMe project (Worker TypeScript) needs to call OpenRouter-backed LLM APIs, including models, chat/completions, streaming, or OpenRouter web search. Guides AI to generate correct Worker TS code.