Contributing
Pull requests welcome. Open an issue first for anything architectural.
Particularly welcome:
- New skill packs that ship opt-in through
configure-skills - New MCP tools that fit the read-mostly, key-gated model
- Linux and Windows hardening, with install notes
- Documentation improvements and more use-case examples
- Translations and regional compliance hints
- New hosts: see what a host needs
Open an issue first for architectural changes. The plugin's contract with the markdown home is intentional and worth preserving.
The dev loop
You run the plugin from your own fork. The fork is where your changes live, and it doubles as the marketplace: the repo ships a developer marketplace (agentlayer-dev) on both hosts, so the checkout registers directly.
Fork the repo
Open AgentLayer1/agentlayer-agent on GitHub and click Fork. Keep the name agentlayer-agent.
Clone your fork
Swap <your-username> for your GitHub username. The second line records the original repo as upstream, which is how your fork stays current:
git clone https://github.com/<your-username>/agentlayer-agent ~/Developer/agentlayer-agent
cd ~/Developer/agentlayer-agent && git remote add upstream https://github.com/AgentLayer1/agentlayer-agentThen, once, install the plugin's packages at the repo root. It takes a minute and about 300 MB, most of it the browser the web tools drive:
cd ~/Developer/agentlayer-agent && bun installInstall from the fork
Register the clone as a marketplace on your host and install the plugin from it. The two commands per host are on Install by hand.
In Claude Code, edits to the fork go live after /reload-plugins, and skill-body edits on the next session; new skills or hooks need a full relaunch. Codex copies the checkout into its plugin cache, so there you remove and re-add the plugin after a change.
Make a change
Work on a branch, never on your fork's main, so main always matches upstream:
cd ~/Developer/agentlayer-agent && git switch -c my-changeMake the change and try it in a session. Before pushing, the checks must pass:
cd ~/Developer/agentlayer-agent
bun src/server.ts # boot check: the banner reports the tool count
bun run typecheck && bun testOpen a pull request
Commit, then push the branch to your fork:
cd ~/Developer/agentlayer-agent && git push -u origin my-changeOn GitHub, open a pull request from that branch in your fork to main on AgentLayer1/agentlayer-agent. GitHub offers Compare & pull request right after the push; with the GitHub CLI it's gh pr create --repo AgentLayer1/agentlayer-agent.
Keep your fork current
Upstream moves on without you. Pull it into your fork's main before starting each change, and after your pull requests merge:
cd ~/Developer/agentlayer-agent && git switch main && git pull --ff-only upstream main && git push origin mainThen bring a branch still in progress up to date by running git merge main on it. If the pull changed package.json, run bun install at the root again. The plugin you run is the fork, so this is also how you update it; finish with the upgrade step to reconcile your home.
Adding a skill: skills/<name>/SKILL.md with frontmatter; grant its MCP tools in the init skill's permission list; use mktemp for scratch files, since $TMPDIR is per-user, not per-session.
Adding an MCP tool: declare it with defineTool from @/shared/tool-def in its domain's src/<domain>/tool.ts. A new domain's tool.ts gets one import line in src/tools.ts. Grant it as mcp__plugin_agentlayer_agent__<tool> in the init skill's permission list, or in its pack's configure-skills walk.
PR conventions: focused changes, update docs when counts change, no unjustified dependencies, typecheck passes. Full detail in CONTRIBUTING.md; the source layout and its rules are in AGENTS.md.
License
Apache 2.0. agentlayer is © AgentLayer. Third-party skill libraries installed through configure-skills are not bundled; each carries its own license, so review the terms before relying on one commercially.