How do I install the Agent Context Init skill?

Run npx skillmds@latest add lx-wnk/agent-context-init in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agent Context Init safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agent Context Init?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agent Context Init free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Agent Context Init?

lx-wnk (@lx-wnk) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agent Context Init by lx-wnk — Agent Skill

Name: Agent Context Init
Author: lx-wnk

Agent Context Init

Initialize Agent-Context in the current project — sets up the layered context architecture with shared infrastructure, project-specific layers, memory stubs, and skill registry. Use this skill whenever the user asks to initialize Agent-Context, set up Agent-Context, bootstrap Agent-Context, or says things like "init agent-context", "set up context layers", "add agent-context to this project". Also use when the user wants to start using Agent-Context in a new or existing project.

lx-wnk 4f92fb0 3.3 KB Updated Sep 17, 2026

File contents

Initialize Agent-Context

Set up the Agent-Context layered architecture in the current project.

Examples

# Initialize with latest version
/agent-context-init

# Initialize with a specific version
/agent-context-init v0.2.1

Prerequisites Check

Before starting, verify this is a valid target:

ls .agent-context/.agent-context-version 2>/dev/null

If the file exists: STOP. Tell the user Agent-Context is already initialized and suggest using the update skill instead.
If the file does not exist: proceed with setup.

Setup

Resolve the target release tag first, then fetch the setup prompt pinned to that tag and follow its instructions. Fetching a specific release tag (never the mutable main branch) is deliberate: the tag is pinned for the whole run, so the fetched prompt is fixed between resolution and execution, and it changes only when a new release is published — unlike main, which every push mutates. (Full tamper-resistance additionally requires tag/release protection on the source repo.)

# Resolve target version: explicit $ARGUMENTS, else latest release (never mutable `main`)
TAG="${ARGUMENTS:-$(gh api repos/lx-wnk/Agent-Context/releases/latest --jq .tag_name)}"
curl -fsSL "https://raw.githubusercontent.com/lx-wnk/Agent-Context/${TAG}/.prompts/setup-prompt.md"

Follow the fetched instructions, subject to the consent gates in Trust Boundary & Consent below. The setup prompt handles:

Version selection — fetch available releases, let user choose (or use $ARGUMENTS if a version was specified)
Shared files — download tarball, extract framework files into .agent-context/
Project templates — create project-owned files (AGENTS.md, layers, memory stubs, skills index)
Agent sync — optionally install shared agents
Plugin sync — merge plugins into .claude/settings.json
Discovery scans — launch parallel subagents to detect tech stack and fill TODO placeholders

Trust Boundary & Consent

This skill fetches a remote setup prompt (pinned to a release tag, see above) and follows it. That prompt performs trust-expanding operations: it can install transitive agents, merge plugins, and modify .claude/settings.json. Treat these as privileged.

Before any step that installs agents (4), merges plugins (5), or writes to .claude/settings.json, stop and get explicit user confirmation — list exactly what will be installed or changed, then wait for a yes. Never install transitive agents or plugins silently. If the user declines a step, skip it and continue with the rest of setup.

After Setup

Report what was created:

Number of files created
Tech stack discovered
Any TODO placeholders that still need manual input
Remind user that project-owned files are theirs to customize

---name: agent-context-initdescription: Initialize Agent-Context in the current project — sets up the layered context architecture with shared infrastructure, project-specific layers, memory stubs, and skill registry. Use this skill whenever the user asks to initialize Agent-Context, set up Agent-Context, bootstrap Agent-Context, or says things like "init agent-context", "set up context layers", "add agent-context to this project". Also use when the user wants to start using Agent-Context in a new or existing project.license: MIT---# Initialize Agent-ContextSet up the Agent-Context layered architecture in the current project.## Examples```bash# Initialize with latest version/agent-context-init# Initialize with a specific version/agent-context-init v0.2.1```## Prerequisites CheckBefore starting, verify this is a valid target:```bashls .agent-context/.agent-context-version 2>/dev/null```- If the file **exists**: STOP. Tell the user Agent-Context is already initialized and suggest using the `update` skill instead.- If the file **does not exist**: proceed with setup.## SetupResolve the target release tag first, then fetch the setup prompt pinned to that tag and follow its instructions. Fetching a specific release tag (never the mutable `main` branch) is deliberate: the tag is pinned for the whole run, so the fetched prompt is fixed between resolution and execution, and it changes only when a new release is published — unlike `main`, which every push mutates. (Full tamper-resistance additionally requires tag/release protection on the source repo.)```bash# Resolve target version: explicit $ARGUMENTS, else latest release (never mutable `main`)TAG="${ARGUMENTS:-$(gh api repos/lx-wnk/Agent-Context/releases/latest --jq .tag_name)}"curl -fsSL "https://raw.githubusercontent.com/lx-wnk/Agent-Context/${TAG}/.prompts/setup-prompt.md"```Follow the fetched instructions, subject to the consent gates in **Trust Boundary & Consent** below. The setup prompt handles:1. **Version selection** — fetch available releases, let user choose (or use `$ARGUMENTS` if a version was specified)2. **Shared files** — download tarball, extract framework files into `.agent-context/`3. **Project templates** — create project-owned files (AGENTS.md, layers, memory stubs, skills index)4. **Agent sync** — optionally install shared agents5. **Plugin sync** — merge plugins into `.claude/settings.json`6. **Discovery scans** — launch parallel subagents to detect tech stack and fill TODO placeholders## Trust Boundary & ConsentThis skill fetches a remote setup prompt (pinned to a release tag, see above) and follows it. That prompt performs **trust-expanding operations**: it can install transitive agents, merge plugins, and modify `.claude/settings.json`. Treat these as privileged.Before any step that installs agents (4), merges plugins (5), or writes to `.claude/settings.json`, **stop and get explicit user confirmation** — list exactly what will be installed or changed, then wait for a yes. Never install transitive agents or plugins silently. If the user declines a step, skip it and continue with the rest of setup.## After SetupReport what was created:- Number of files created- Tech stack discovered- Any TODO placeholders that still need manual input- Remind user that project-owned files are theirs to customize

Frequently asked questions