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 agentmods add skills/corezoid/corezoid-ai-plugin/corezoid-variable-managernpx skills add corezoid/corezoid-ai-plugin --skill corezoid-variable-managergit clone --depth 1 https://github.com/corezoid/corezoid-ai-pluginWrote 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/corezoid/corezoid-ai-plugin/corezoid-variable-manager)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/corezoid-variable-manager"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-variable-manager.svg" alt="Measured on agentmods" 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 | $0.00123 | $0.03854 |
| Opus 5 | $0.00062 | $0.01927 |
| Sonnet 5 | $0.00025 | $0.00771 |
| Haiku 4.5 | $0.00012 | $0.00385 |
Grade A, and why
corezoid-variable-manager 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 5d 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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corezoid Variable Manager
What variables are
Environment variables store constants (URLs, tokens, API keys, IDs, configuration values)
that must not be hardcoded in process logic. The reference syntax {{env_var[@name]}} is
resolved at runtime — changing a variable value takes effect immediately without
redeploying any process.
Variables are stage-scoped: shared across all processes within a stage.
Variable types
By data type
data_type |
When to use | Value format |
|---|---|---|
raw |
Plain string (URL, token, ID, any scalar) | "https://api.example.com" |
json |
Structured config, multi-field config, feature flags | {"key":"value","nested":{...}} |
By visibility
env_var_type |
UI display | Accessible from | Scopes |
|---|---|---|---|
visible |
Value shown in plain text | All node types | [{"type":"*","fields":"*"}] |
secret |
Value masked, shows only fingerprint | API Call nodes only | [{"type":"api_call","fields":"*"}] |
⚠️ Secret variables are designed for tokens, passwords, and API keys. They are never returned in plain text by the API after creation — only an MD5/SHA256 fingerprint is available. Use
visiblefor non-sensitive configuration.
MCP Tools
| Tool | Purpose |
|---|---|
create-variable |
Create a raw + visible variable in one step |
list-variables |
List a stage's variables with obj_id, types, values (secrets masked) |
modify-variable |
Change value/title/data_type or rename — dry-run + confirm-gated |
delete-variable |
PERMANENTLY delete (no recycle bin) — dry-run + confirm-gated |
Note: creating
secretorjsonvariables is not yet exposed as an MCP tool — use the direct API calls documented below for creation; manage them afterwards with the tools above.
Double-confirmation etiquette (modify / delete)
modify-variable and delete-variable are consequential: a deleted variable is gone
FOREVER (env vars have NO recycle bin), a renamed one breaks every
{{env_var[@old-name]}} reference, and a changed value takes effect immediately in
running processes. The tools enforce a two-step gate, and you must drive it honestly:
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.
- 5d ago First seen · 451 lines · 123 tokens per session scan A d27de666efd9
corezoid-variable-manager is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (73 stars, last pushed yesterday), licensed MIT. It adds 123 tokens to every session and 3,854 once invoked, about $0.0006 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
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.
stss
Reduce defensive disclaimers, stacked hedging, and self-protective narration in proposals and decision-facing writing. Use when the user asks to rewrite or audit a proposal, plan, research contribution, executive summary, or similar text for directness. Do not use for ordinary code work or unrelated prose.