MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
A skill your agent uses when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Install Agentlas Auto Activation
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agentlas-ai/Agentlas-OS agentlas-auto-activation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agentlas-auto-activation .claude/skills/agentlas-auto-activation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "agentlas-auto-activation" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/agentlas-auto-activation into .claude/skills/agentlas-auto-activation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentlas-auto-activation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/agentlas-auto-activationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agentlas-ai/Agentlas-OS agentlas-auto-activation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/agentlas-auto-activation .agents/skills/agentlas-auto-activation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agentlas-auto-activation" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/agentlas-auto-activation into .agents/skills/agentlas-auto-activation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentlas-auto-activation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agentlas-ai/Agentlas-OS agentlas-auto-activation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/agentlas-auto-activation .cursor/skills/agentlas-auto-activation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "agentlas-auto-activation" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/agentlas-auto-activation into .cursor/skills/agentlas-auto-activation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentlas-auto-activation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/agentlas-ai/Agentlas-OS.git --path skills/agentlas-auto-activation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agentlas-ai/Agentlas-OS agentlas-auto-activation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/agentlas-auto-activation .gemini/skills/agentlas-auto-activation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "agentlas-auto-activation" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/agentlas-auto-activation into .gemini/skills/agentlas-auto-activation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentlas-auto-activation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install agentlas-ai/Agentlas-OS agentlas-auto-activationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/agentlas-auto-activation .github/skills/agentlas-auto-activation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "agentlas-auto-activation" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/agentlas-auto-activation into .github/skills/agentlas-auto-activation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentlas-auto-activation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agentlas-ai/Agentlas-OS agentlas-auto-activation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/agentlas-auto-activation .opencode/skills/agentlas-auto-activation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "agentlas-auto-activation" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/agentlas-auto-activation into .opencode/skills/agentlas-auto-activation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentlas-auto-activation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
agentlas-auto-activation- GitHub stars
- 1.6k
- Token cost
- ~559 tokens
- SKILL.md length
- 225 words
- Files
- 1
- Skills in repo
- 53
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
- Works in 9 steps: For explicit activation, call hephaestus… → For automatic activation, require a… → Never create project state in the user's… → …
- Auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files
- SKILL.md covers Procedure, Minimum Files, Safety and Reference
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Agentlas Auto Activation is an agent skill from agentlas-ai/Agentlas-OS. Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. The repository describes itself as: Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model. The licence is Apache-2.0.
When your agent uses it
- Auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files
Example prompts
- “/agentlas-auto-activation”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- For explicit activation, call hephaestus project ensure --project
- For automatic activation, require a trusted writable host, an allowed root,
- Never create project state in the user's home directory, filesystem root, or
- Install the managed privacy .gitignore block before local memory/indexes.
- Add missing seed files, ontology/career indexes, and the bounded code map
- Inject relevant project memory into future agent prompts.
- Ask workers to emit ## Memory Events only for durable facts.
- Route Memory Events through Memory Tickets and Memory Curator.
- Use sitemap/task-bias state to avoid stale or unvalidated surfaces.
What it can do on your machine
Read from SKILL.md and the folder at commit 6254906. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Agentlas Auto Activation loads about 559 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 225 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from agentlas-ai/Agentlas-OS at commit 6254906, republished under its Apache-2.0 licence (© agentlas-ai). 225 words, ~559 tokens.
Download SKILL.mdSave it as
.claude/skills/agentlas-auto-activation/SKILL.md (or your agent's skills folder).- name
- agentlas-auto-activation
- description
- Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Agentlas Auto-Activation
Use this skill when a local runtime should activate Agentlas project continuity for a folder.
Procedure
- For explicit activation, call
hephaestus project ensure --project <folder>from Agentlas Core. - For automatic activation, require a trusted writable host, an allowed root, a workspace marker, and host-side opt-in. Passive search, read-only work, and MCP requests do not imply write consent.
- Never create project state in the user's home directory, filesystem root, or outside the host's allowed project roots.
- Install the managed privacy
.gitignoreblock before local memory/indexes. - Add missing seed files, ontology/career indexes, and the bounded code map without overwriting existing user content.
- Inject relevant project memory into future agent prompts.
- Ask workers to emit
## Memory Eventsonly for durable facts. - Route Memory Events through Memory Tickets and Memory Curator.
- Use sitemap/task-bias state to avoid stale or unvalidated surfaces.
Minimum Files
.agentlas/project-soul-memory.md.agentlas/sitemap.json.agentlas/memory-map.json.agentlas/memory-tickets.jsonl.agentlas/vault-references.json.agentlas/skill-registry.json.agentlas/skill-trials.jsonl.agentlas/curator-decisions.jsonl.agentlas/activation.json.agentlas/code-map/project-map.json.agentlas/ontology-runtime.json.agentlas/ontology-runtime.sqlite.agentlas/career-graph.json.agentlas/career-graph.sqlite
Safety
Never store secrets, raw logs, full transcripts, cookies, private keys, service
accounts, or payment material in .agentlas.
Keep MCP auto-bootstrap disabled unless the host separately opts in. Automatic receipts must not expose absolute project paths or raw filesystem errors.
If private files were already tracked before activation, report them as
trackedSensitivePaths; never mutate the user's Git index automatically.
Reference
See docs/agentlas-auto-activation.md.
© agentlas-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/agentlas-auto-activation of agentlas-ai/Agentlas-OS.
Open the folder on GitHubat commit 6254906
Compare with similar skills
Agentlas Auto Activation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Agentlas Auto Activation this skillagentlas-ai/Agentlas-OS | 1.6k | — | ~559 | Automated safety check: Pass | Apache-2.0 | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 795 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
More from agentlas-ai/Agentlas-OS
All 53 skills in this repoAgentlas Security Scan
agentlas-ai/Agentlas-OS
A skill your agent uses when an agent folder must pass the Agentlas Cloud 2-stage security scan (static rules + BYOK LLM judgment) before private sync or public publish, or when asked to…
Hephaestus Build
agentlas-ai/Agentlas-OS
A skill your agent uses when the user types /prompts:hep-build or /agentlas-build, mentions @Hephaestus for build work, asks to create a single Agentlas agent, create a multi-agent team, or package…
Hephaestus Graph
agentlas-ai/Agentlas-OS
A skill your agent uses when the user types /hep-graph or asks to create, list, inspect, or request a run of an Agentlas automation graph.
Hephaestus Upload
agentlas-ai/Agentlas-OS
A skill your agent uses when the user types $hephaestus-upload, /hep-upload, or /agentlas-upload, or asks to upload, publish, or list an Agentlas agent or team.
Routing Card Authoring
agentlas-ai/Agentlas-OS
A skill your agent uses whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager.
Team Builder Packaging
agentlas-ai/Agentlas-OS
A skill your agent uses when generating or auditing a multi-role agent team package with orchestrator, PM Soul, Memory Curator, Policy Gate, workers, eval, QA, handoffs, and runtime adapters.
Related
Categories
Questions about Agentlas Auto Activation
What does Agentlas Auto Activation do?
A skill your agent uses when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files. Agentlas Auto Activation is an agent skill from agentlas-ai/Agentlas-OS.agentlas memory and sitemap files.
When should I use Agentlas Auto Activation?
Agentlas Auto Activation fits situations like: auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
How do I install Agentlas Auto Activation in Claude Code?
Run `npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a claude-code`. Or copy the skill folder (skills/agentlas-auto-activation in agentlas-ai/Agentlas-OS) into .claude/skills/agentlas-auto-activation in your project. Claude Code loads it when a task matches its description.
How do I install Agentlas Auto Activation in Codex?
Run `npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a codex`. Or copy the skill folder (skills/agentlas-auto-activation in agentlas-ai/Agentlas-OS) into .agents/skills/agentlas-auto-activation in your project. Codex loads it when a task matches its description.
Can I use Agentlas Auto Activation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agentlas-ai/Agentlas-OS --skill agentlas-auto-activation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agentlas-auto-activation, .gemini/skills/agentlas-auto-activation, .github/skills/agentlas-auto-activation and .opencode/skills/agentlas-auto-activation in your project.
What does Agentlas Auto Activation need to run?
SKILL.md names no scripts, command-line tools or credentials: Agentlas Auto Activation is instructions for the agent only.
Does Agentlas Auto Activation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Agentlas Auto Activation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Agentlas Auto Activation use?
Agentlas Auto Activation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Agentlas Auto Activation use?
About 559 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Agentlas Auto Activation?
Skills that share tags, products or a category with Agentlas Auto Activation: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Agentlas Auto Activation?
agentlas-ai (a GitHub organization) maintains it in agentlas-ai/Agentlas-OS, which has 1,582 GitHub stars. The repository holds 53 skills in this directory. The repository was last updated on October 8, 2026.
Source: agentlas-ai/Agentlas-OS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.