Agent context init

Skill lx-wnk/skills/skills/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.From its SKILL.md

Install

npx -y skills add lx-wnk/skills --skill agent-context-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.5 KB, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most project setup skills give

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

Write the configuration filein 36 of 1553
Create the directory structurein 35 of 1553, across 33 files
Verify the setupin 31 of 1553, across 28 files
Run the setup scriptin 30 of 1553, across 29 files
Pre-determine the required sample sizein 29 of 1553, across 12 files
Check if the configuration already existsin 29 of 1553
Document every testin 26 of 1553, across 10 files
Start with a hypothesisin 26 of 1553, across 11 files
Ask one question at a timein 22 of 1553
Test a single variable per testin 21 of 1553, across 9 files
Read product marketing context before asking questionsin 19 of 1553, across 8 files
Do not peek and stop earlyin 18 of 1553, across 7 files

Said here and by no other author read

Resolve target version from arguments or latest release
Fetch the setup prompt pinned to the target tag
Get explicit user confirmation before privileged steps
Report what files and tech stack were created

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.