ci

A command that restores skills and MCP servers from saved lockfiles. Lockfiles record the exact installed setup so it can be reproduced.

In plain words
What is it for?
Use it in automated builds or onboarding to reinstall all recorded skills and MCP servers.
Why use it?
It helps CI systems and new team members recreate the same agent setup after a repository is cloned.

Command

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.

agentmods
npx agentmods add commands/rolecraft-sh/rolecraft/ci
Clone the repo
git clone --depth 1 https://github.com/rolecraft-sh/rolecraft
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 184 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00184
Opus 5 $0.00000 $0.00092
Sonnet 5 $0.00000 $0.00037
Haiku 4.5 $0.00000 $0.00018

Measured 3d ago against content hash 4275f6cb97fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ci 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 3d 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.

docs/commands/ci.md · 32 lines

What it actually says

rolecraft ci

Re-install all skills and MCP servers from lockfile (CI mode).

Usage

rolecraft ci

Description

Reads both the skill lockfile (~/.agents/.skill-lock.json) and the MCP lockfile (~/.agents/.mcp-lock.json) and re-installs everything, ensuring the installed state matches the locked state exactly.

Designed for CI pipelines and team onboarding — run this after cloning a repository to restore all project skills and their required MCP servers.

Example

# In CI or after git clone — restores skills + MCP servers
rolecraft ci

Node.js API

This command is also available as a programmatic function. See the Node.js API documentation for detailed usage.

import { ci } from 'rolecraft'
const result = await ci()
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. 3d ago First seen · 32 lines · 0 tokens per session scan A 4275f6cb97fa

Subscribe to this mod's changes

ci is a command published in the GitHub repository rolecraft-sh/rolecraft (75 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 184 tokens. 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.