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 brcampidelli/chimera-agent --skill declare-when-a-setting-takes-effectgit clone --depth 1 https://github.com/brcampidelli/chimera-agentWrote 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/brcampidelli/chimera-agent/declare-when-a-setting-takes-effect)<a href="https://agentmods.dev/skills/brcampidelli/chimera-agent/declare-when-a-setting-takes-effect"><img src="https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/declare-when-a-setting-takes-effect/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/brcampidelli/chimera-agent/declare-when-a-setting-takes-effect"><img src="https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/declare-when-a-setting-takes-effect.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.00041 | $0.00612 |
| Opus 5 | $0.00020 | $0.00306 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
declare-when-a-setting-takes-effect 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger
You are exposing a setting in a user interface, and the code that consumes it reads the value at some point other than every use: at process start, when a session is built, or into a cached object.
It does not apply to a setting read on every use. Those apply immediately and should say nothing — a note about a delay that does not exist teaches the same distrust as a missing one.
Do
- For each setting, find the line that reads it. When it applies is a property of that line, not of the control.
- Prefer making it read live. A property that resolves on access usually costs nothing and removes the problem instead of describing it.
- Where it genuinely cannot — something is started at boot — label it, and generate the label from the server or the same module that knows the read site, so the label cannot drift.
- Group the labels into meaningful classes: applies now, applies to your next conversation, applies after a restart.
Avoid
A settings screen that confirms a save and quietly does nothing. It is worse than an error: an error sends the user to look for a cause, while a success sends them to blame the feature, the model, or themselves.
Avoid hard-coding the list of "needs a restart" in the interface. That list is a copy of knowledge that lives elsewhere, and it goes stale the first time a read site moves — silently, which is how the original problem was created.
Avoid a blanket "some settings require a restart" note. It is true, unhelpful, and covers the ones that do not.
Check
Change the setting, use the feature, and observe the behaviour — not the screen. Read a value back from the running system, not from the form you just submitted.
The mechanical version: assert that no setting is labelled as immediate, and that every setting the interface exposes appears in the classification the server publishes.
Risk
Labels add noise to a settings screen, and a screen where every row has a badge is a screen where badges mean nothing. Only the delayed ones need one.
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 · 67 lines · 41 tokens per session scan A 2f1c9fd86ac2
declare-when-a-setting-takes-effect is a skill published in the GitHub repository brcampidelli/chimera-agent (22 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 612 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-30.
Other skills, from other repositories
weknora-shared
Use when driving a WeKnora RAG server through the weknora CLI as an agent — authenticating, managing knowledge bases / documents / sessions / agents, running search or chat, or interpreting the CLI's JSON envelopes and exit codes. Read this before any other weknora- skill.
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).
llm-wiki
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) in plain markdown. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing a wiki source's reasoning, superseding stale knowledge, 'add to…
home-assistant
This skill should be used when helping with Home Assistant setup, including creating automations, modifying dashboards, checking entity states, debugging automations, and managing the smart home configuration. Use this for queries about HA entities, YAML automation/dashboard generation, or troubleshooting HA issues.
authoring-claude-md
Creating and maintaining CLAUDE.md project memory files and .claude/rules/ rule files that provide non-obvious codebase context. Use when (1) creating a new CLAUDE.md for a project, (2) adding architectural patterns or design decisions to existing CLAUDE.md, (3) capturing project-specific conventions that aren't…
find-skills
Helps users discover agent skills from the open skills ecosystem. Use when users ask "how do I do X", "find a skill for X", "is there a skill that can...", or want to extend agent capabilities. This skill searches for and evaluates candidate skills, then presents findings to the user for them to review and decide…