component-management

component-management is a skill for Claude Code, Codex from zylos-ai/zylos-core. It costs 37 tokens per session (1,592 once invoked), scanned A, original, MIT.

A set of procedures for managing Zylos components, which are installable parts of the Zylos system. It covers the command-line tool and coordination through C4 channels, a messaging system used by the components.

In plain words
What is it for?
Use it to list installed components, search available ones, check versions and status, and guide approved installation, upgrade, or uninstall operations.
Why use it?
It provides a consistent process for installing, upgrading, or removing components while checking requirements and preserving data. It also requires confirmation before these changes are executed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to list installed components, search available ones, check versions and status, and guide approved installation, upgrade, or uninstall operations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zylos-ai/zylos-core/component-management
About the project

Zylos is open-source infrastructure that gives an AI agent persistent memory, scheduled activity, communication channels, and the ability to maintain and extend itself. Individuals and teams use it with Claude Code or Codex through Telegram, Lark, or a web console. Its catalogue add-ons define settings, instructions, and skills for operating the agent.

zylos-ai/zylos-core · 1,151 stars · on GitHub · zylos.ai

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 zylos-ai/zylos-core --skill component-management
Clone the repo
git clone --depth 1 https://github.com/zylos-ai/zylos-core

Made for: Claude Code, Codex.

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 component-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/zylos-ai/zylos-core/component-management/github.svg)](https://agentmods.dev/skills/zylos-ai/zylos-core/component-management)
Your own site
<a href="https://agentmods.dev/skills/zylos-ai/zylos-core/component-management"><img src="https://agentmods.dev/badge/skills/zylos-ai/zylos-core/component-management/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 component-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/zylos-ai/zylos-core/component-management"><img src="https://agentmods.dev/badge/skills/zylos-ai/zylos-core/component-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,592 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original 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.00037 $0.01592
Opus 5 $0.00018 $0.00796
Sonnet 5 $0.00007 $0.00318
Haiku 4.5 $0.00004 $0.00159

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

Security

Grade A, and why

component-management 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 11d 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.

skills/component-management/SKILL.md · 155 lines

How it starts

The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Component Management

Guidelines for installing, upgrading, and managing zylos components.

CLI

zylos is a global npm command (installed via npm install -g zylos). Run it directly as zylos, NOT as ~/zylos/zylos or ./zylos.

General Principles

  1. Always confirm before executing - User must explicitly approve install/upgrade/uninstall
  2. Guide interactively - Never just tell user to "manually edit files"
  3. Read SKILL.md - Each component declares its requirements in SKILL.md frontmatter
  4. Detect execution mode - Handle both Claude session and C4 channels differently
  5. CLI = mechanical, Claude = intelligent - CLI handles downloads, backups, file sync. Claude handles config, hooks, service management, user interaction.

Workflows

Detailed step-by-step workflows for each operation (Session + C4 modes):

  • Install — Add new components
  • Upgrade — Upgrade components and zylos-core (self-upgrade)
  • Uninstall — Remove components with data options

Quick Commands

# Check zylos-core version
zylos --version

# List installed components (with versions)
zylos list

# Search available components
zylos search <keyword>

# Component status
zylos status

# Check for zylos-core updates
zylos upgrade --self --check

# Check for beta/prerelease updates
zylos upgrade --self --check --beta

# Check all components for updates
zylos upgrade --all --check

SKILL.md Config Format

Components declare their configuration requirements in SKILL.md frontmatter:

---
name: my-component
version: 1.0.0
description: Component description

config:
  required:
    - name: ENV_VAR_NAME
      description: Human-readable description
      sensitive: true  # Optional: marks as secret
  optional:
    - name: OPTIONAL_VAR
      description: Optional setting
      default: "default-value"
---

When sensitive: true, the value should be handled carefully and not logged.

Read the full file on GitHub · 155 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 155 lines · 37 tokens per session scan A fc38c102b503

Subscribe to this mod's changes

component-management is a skill published in the GitHub repository zylos-ai/zylos-core (1,151 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 1,592 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.