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 Bilal140202/the-lord-of-the-skills --skill agentcontrol-configs-updategit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/agentcontrol-configs-update)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/agentcontrol-configs-update"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/agentcontrol-configs-update/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/bilal140202/the-lord-of-the-skills/agentcontrol-configs-update"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/agentcontrol-configs-update.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.00044 | $0.00903 |
| Opus 5.5 | $0.00018 | $0.00361 |
| Sonnet 5.5 | $0.00009 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
configs-update 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Update & Lifecycle
You're using a skill that will guide you through updating, archiving, and deleting configs and their variations. Your job is to understand the current state of the config, make the changes, and verify the result.
Prerequisites
This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment.
Required MCP tools:
get-ai-config-health-- assess config health before making changes (detects missing models, orphaned tools, empty configs)get-ai-config-- understand current state before making changesupdate-ai-config-- update config metadata (name, description, tags, archive)update-ai-config-variation-- update variation model, prompts, or parameters
Optional MCP tools:
delete-ai-config-- permanently delete a config (irreversible)delete-ai-config-variation-- permanently delete a variation (irreversible)
Core Principles
- Fetch Before Changing: Always check the current state before modifying
- Verify After Changing: Fetch the config again to confirm updates were applied
- Archive Before Deleting: Archival is reversible; deletion is not
Workflow
Step 1: Assess Health and Understand Current State
Start with get-ai-config-health to get a structured health assessment. This detects:
- Variations with no model (show as "NO MODEL" in the UI)
- Variations with neither instructions nor messages
- Orphaned tool references (tools attached that don't exist in the project)
- Configs with no variations at all
The health verdict (healthy, warning, unhealthy) helps you prioritize what to fix.
Then use get-ai-config to review the full detail:
- Current mode (agent or completion)
- Existing variations and their models
- Current instructions or messages
- Attached tools and parameters
Step 2: Make the Update
Update config metadata -- Use update-ai-config:
- Change name or description
- Add or replace tags
- Archive with
archived: true(reversible)
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 · 95 lines · 44 tokens per session scan A 112954933164
configs-update is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 903 once invoked, about $0.0002 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-09-06.
Other skills, from other repositories
roo-fix-volatile-msg
Ladder-aware Roo Code Anthropic caching — verify the rolling read/write ladder on the wire, then close the real gaps (Vertex 4-block budget, MiniMax path).
prompt-engineering
Use when one prompt must give the same right answer across reruns, models, and pasted-in hostile input: forcing a fixed schema, picking the few-shot set, ordering the prompt blocks, or the inline cases you run while tuning. NOT the agent loop, tools, or retrieval (that is building-agents), NOT a standing CI eval…
llm-runtime
Integrate, stream, and orchestrate frontier LLM APIs with robust structured outputs, tool call schemas, prompt caching, and resilient backoff handling. Use when implementing AI agent runtimes, tool-calling loops, streaming SSE endpoints, or optimizing token usage and model latency.
kling-prompter
A prompt-writing guide for Kling 3.0, a video-generation model. It covers short videos, story-driven videos with dialogue or sound, and animating an existing reference image.
happyhorse-prompter
A tool for writing short prompts for HappyHorse 1.0, an AI video generator that can create video with sound. Its prompts put the main subject first, specify the camera, and describe audible sound when needed.
few-shot-example-gen
Few-shot example generation and optimization for improved LLM performance.