Setup library

The setup library is the shared catalogue of agent setups that projects have published. An agent setup is a named bundle of what your AI coding tools work with: skills, agents, rules, MCP servers and setup files. You can add an entry to a project as a new setup, or merge its content into a setup the project has.

A library entry is one published setup. It holds a full copy of that setup as it was when its publisher last published it.

Part of an entry	What it is
Skills	Reusable sets of instructions that an AI tool loads when they are relevant, usually run as a slash command such as /atn-mindmap. Each skill comes with its bundle files.
Agents	Specialists that an AI tool can hand work to (subagents in most AI tools).
Rules	The instructions every agent in the setup follows.
MCP servers	Connections to external tool servers, with their configuration.
Setup files	Extra Markdown files, including the settings files under settings/.

An entry also has a name that is unique in the library, a description, tags, a publisher, a version number that rises with each publication and a count of likes. Entries are published by Athenode projects and by Athenode. The standard Athenode setup is an entry too, marked Standard.

Browse and search the setup library

Any signed-in user can browse the library, on every plan and with any role. Without an account, the library catalogue on the Athenode website shows entries whose public display is on.

1. Open Library in the sidebar. Inside a project, you can also open Setups and select Browse library.
2. Enter a word in the field Search by name, description or tag.
3. Select a tag on a card to keep only the entries that carry it.
4. Select Load more to see further entries.

Each card shows the entry's name, its version as "v" and a number, its publisher, how many agents, skills, MCP servers and files it holds, and its likes. The Standard entry comes first, followed by the other entries with the most liked first.

The library shows the entries as they were when you opened the page. Reload the page to see what was published since.

Read an entry before you use it

An installed setup instructs your AI coding agent inside your repository, so read what an entry contains before you add or merge it.

1. Open the entry from its card.
2. Select an agent, a skill, an MCP server, a file or the rules to open it in a read-only viewer.
3. In a skill, open Bundle files to read the files that come with it.

Signed-in users see the whole entry, including the configuration of its MCP servers: commands, arguments, URLs and the names of the environment variables each server needs.

Like an entry

You like an entry in the web app, from its card or its page. Select the heart to add your like and select it again to take it back. Each user gives an entry one like, and the likes decide the order of the library.

Add an entry as a new setup

Add an entry as a new setup when you want the whole setup next to the ones your project has, and want to be told when its publisher releases a newer version.

You need the owner or editor role in the project, and the project needs room for one more setup. A project holds 1 setup on the Free plan, 5 on Solo and 10 on Team, with no limit on Business. A project on the Free plan already holds its copy of the standard setup, so there you merge the entry into that copy. The entry must also fit the plan's limits on skills, agents and MCP servers per setup, which Plans and limits lists.

1. On the entry, select Use in project.
2. If you opened the library from the sidebar, choose the project in Project. The list holds the projects where you are the owner or an editor.
3. Choose Add as a new setup and select Continue.
4. In Setup name, keep the entry's name or enter your own. If the project has a setup with that name, the dialog offers a free name on a button. Select it to use that name.
5. Select Add setup.

Athenode confirms with "Setup '<name>' added." The project has a new setup with a full copy of the entry, including its settings files exactly as they were published. If the setup doesn't fit the project's plan, Athenode shows Plan limit reached and creates nothing. The owner can upgrade the plan from that dialog.

Adding a setup changes nothing in your local project directory. To work with the new setup, install it:

npx @athenode/cli init --setup <id-or-slug>

Restart your AI tool after the install so that it loads the new skills, agents and MCP servers. The settings files of the entry describe its publisher's project, so run /atn-settings once to replace them with your own choices for testing, code review and git.

If you belong to no project where you are the owner or an editor, the entry shows "To use this setup, create a project of your own." with the button Create a project.

Merge an entry into a setup

Merge an entry when you want some of its items inside a setup you already work with, or when the project is on the Free plan. You need the owner or editor role in the project. Merging is possible on every plan.

1. On the entry, select Use in project.
2. If you opened the library from the sidebar, choose the project in Project.
3. Choose Merge into an existing setup and select Continue.
4. In Target setup, choose the setup to merge into and select Continue. Your project's copy of the standard setup is labelled Copy of the standard setup.
5. On the review page, go through Skills, Agents, MCP servers and Files. Every new item is selected. Clear the ones you don't want.
6. For each conflict, choose Keep mine or Replace with the library one. Select Compare to see your version next to the library's.
7. Under Rules, choose Keep mine, Append the library rules or Replace with the library rules.
8. Check the summary of items to add and items to replace, then select Merge.
9. If you chose to replace anything, Athenode asks "Replace these items?". Select Replace and apply.

Athenode confirms that the entry was merged into the setup. The review page sorts the entry's content into new items, conflicts and identical items:

• New items are items your setup doesn't have. They are added unless you clear them.
• Conflicts are items your setup has under the same name, or files at the same path, with different content. Keep mine is the default. A conflict marked Cannot be replaced states its reason and can only be kept.
• Identical items are the same on both sides. Nothing is written for them.

A setup has one rules text, so the rules are a single choice. Append the library rules adds them after yours, under a heading with the entry's name, and is unavailable when the result would be longer than 50,000 characters.

A merge adds and replaces items and deletes nothing from your setup. It is applied as a whole, so if the added skills, agents or MCP servers would take the setup past a limit of the project's plan, nothing is written. Replacing an item doesn't count towards those limits. A replaced skill or agent changes in this setup only, and other setups of the project that use the same skill or agent keep their version.

If the setup or the entry changes while you are on the review page, Athenode loads the preview again and asks you to check your choices before you apply them.

A merged setup has no link to the entry afterwards, so it shows no update when the entry gets a newer version. To get later changes, merge again. If you merged into the installed setup, run init again to bring the changes into your local project directory.

Update a setup added from the library

A setup that you added as a new setup remembers its entry and the version it was copied from. When the publisher releases a newer version, the setup shows Update available with a line such as "Version 4 of the library setup is out. This setup is on version 3." You need the owner or editor role to update.

1. Open Setups and select the setup that shows Update available.
2. Optional: select Show what changed to read the publisher's note for each newer version.
3. Select Update.
4. On the review page, make the same choices as for a merge: clear new items you don't want, decide each conflict and choose what happens to the rules.
5. Select Update. If you chose to replace anything, confirm with Replace and apply.

Athenode confirms that the setup was updated to the new version. An update adds and replaces items and deletes nothing from your setup, so an item the publisher removed stays with you until you remove it. Run init again to bring the updated setup into your local project directory.

Skip this version hides the notice until the entry gets another version. You skip a version in the web app.

If the publisher unpublishes the entry, your setup keeps working as an ordinary setup and receives no further updates.

Use the library from your AI tool or the terminal

From your AI tool, ask /atn-manage in plain words to browse the library, show an entry, add it, merge it or update a setup. The skill asks you before it replaces anything.

From the terminal, the Athenode CLI has a command for each task. An entry is named by its exact name, and a setup with --setup and its exact name.

Task	Command
Browse and search	athenode library list
Read an entry or one of its items	athenode library get, athenode library item
Add an entry as a new setup	athenode library add
Merge an entry into a setup	athenode library merge-preview, athenode library merge
Update a setup added from the library	athenode library update-preview, athenode library update

npx @athenode/cli library add "Security review"

The command prints the id of the new setup, which you pass to init --setup. A merge or an update run without your decisions adds every new item, replaces nothing and keeps your rules. When the target is the installed setup, the CLI also updates the files in your local project directory.

The same commands are available to your AI agent as the library_* tools of the Athenode MCP server.

A library entry can also be the source when you pull from another setup, which opens the same review page. To share a setup of your own, see how to publish a setup.