The Codex install prompt: AiAkiv connection and skills in one go

Paste it into a Codex chat and Codex registers the AiAkiv connection, opens the sign-in window, installs the seven skills and writes an install record on its own. No developer mode needed. Before pasting, remove the existing AiAkiv Memory plugin, or, if you keep it, rename this connection to AiAkivCodex.

Paste the prompt below into a Codex chat as it is, and Codex does the following on its own.

  1. Registers the address https://mcp.aiakiv.com/mcp?apps=all as an MCP server named AiAkiv.
  2. Opens the sign-in window (OAuth). A person does the sign-in.
  3. Installs the seven AiAkiv skills from the public repository github.com/AiAkiv/aiakiv-plugins into ~/.agents/skills/.
  4. Writes an install record (aiakiv-install-test.md) in the working folder.

No developer mode is needed. This prompt passed a real run on 2026-10-13. Once the install is done, open a new session and check it with the Codex verification prompt.

Why this is installed separately from the plugin, and what this connection gives you, is in Connecting ChatGPT §6.

Before you paste

  • If you installed the AiAkiv plugin before (AiAkiv Memory from the plugin directory), remove it first where you can. The two connections expose tools with the same names, so the AI picks whichever it likes, and the plugin side has no app action tool, so the tools the skills call are missing there.
  • If you keep the plugin, name this connection AiAkivCodex. If you also want the plugin in chatgpt.com web chats, leave it installed and change the MCP name AiAkiv in the prompt below to AiAkivCodex before pasting. Then you can say which one to use, as in "save it through AiAkivCodex".
  • A person signs in. When the sign-in window appears, sign in with your www.aiakiv.com account and give consent. Codex does not sign in for you.

The prompt

Codex follows the prompt in English just as well as the Korean original.

Install AiAkiv's MCP server and skills for Codex on this PC and complete the OAuth connection. Do not assume a fixed executable location or user name, since these differ from PC to PC.
What to install:

* MCP name: AiAkiv
* MCP URL: https://mcp.aiakiv.com/mcp?apps=all
* Skills repository: https://github.com/AiAkiv/aiakiv-plugins
* Install scope: the Codex global settings and skills of the current OS user

Carry out the following steps yourself, in order.

1. Check the current user, the working folder and where the Codex settings live. If CODEX_HOME is set, check its value, and find the config.toml actually in use. Do not print the whole configuration if it contains credentials.
2. Find the Codex CLI. Check PATH first; if it is not there, find where the Codex app is actually installed and the executable bundled with it. Do not guess user names or version-specific folder names. Check the version of the executable you found and call it by its full path from then on. If you cannot find the CLI, check whether you can proceed through the app settings, and tell me which parts need me to act.
3. Check whether the AiAkiv MCP server and skills are already installed. If an identical item exists, do not install it twice. If an earlier install record differs from the current state, investigate the difference in settings locations. If the AiAkiv Memory plugin installed from the plugin directory is still there, the tool names collide, so stop and tell me to either remove the plugin and start again, or change the MCP name to AiAkivCodex if I want to use both.
4. Register AiAkiv in the current user's Codex global settings. If an existing entry has the right name and URL, keep it. Preserve all other settings. Do not change CODEX_HOME on your own.
5. Using the same executable and settings environment, list the MCP servers and confirm that AiAkiv appears. Then carry out the OAuth authentication it needs. I will complete the sign-in and consent myself.
6. If an HTTP request fails, investigate the cause. Also check whether the environment running the commands has network restrictions, and if a supported approval step is needed, explain why and proceed.
7. Check the repository structure and install all of the AiAkiv skills. Do not newly install Node.js or npx; use the built-in skill-installer, or download the ZIP and copy the files. Keep the reference files that sit next to each SKILL.md. If a skill is already installed, check how its version or contents differ, and explain why it needs replacing.
8. Write aiakiv-install-test.md in the current working folder, or update the existing record. Record the executable path you found, the actual settings location, the names and locations of the skills you installed, the MCP registration status, the OAuth result, and any errors and how they were resolved. Do not record tokens, passwords or authorization codes.
9. After installing, check whether the tools and skills appear in the current session. If a new session is needed, tell me, and give me a check prompt that calls AiAkiv's get_save_target in the new session.

Do not save memories, create cards or edit Contents. At the end, briefly list what was completed and what is left for me to do.

Good to know

  • Seven skills are installed. aiakiv-onboarding, aiakiv-save-and-recall, aiakiv-graph-query, aiakiv-links, aiakiv-cards, aiakiv-console, aiakiv-contents. Each goes into ~/.agents/skills/<skill name>/. That is the same path as the skills in the console's folder ZIP.

  • Doing it by hand takes two lines. To do it yourself in a terminal instead of asking Codex, run the two lines below. The first registers the connection and the second installs the seven skills. If you keep the plugin, change AiAkiv in the first line to AiAkivCodex. Don't give --all to the Skills CLI in the second line: it scatters skill links into every agent's folder.

    codex mcp add AiAkiv --url "https://mcp.aiakiv.com/mcp?apps=all"
npx skills add AiAkiv/aiakiv-plugins -a codex -s '*' -g -y

  • To see whether the skills are really read, run codex debug prompt-input "hello". Codex prints the prompt it would send to the model; the seven names should be in its skill list. It doesn't call the model, so it uses no quota.

  • Check the connection in a new session. Paste the Codex verification prompt and it checks the tools, the save location and the skills one by one.

  • Saving goes to Main. This connection follows the Main project set in the console. To pin a project per folder, use a project-pinned API key → Connecting ChatGPT §2.

  • The AI only does the console changes you turned on. It can only do what you turned on in Reference → AI permissions in the console → Asking your AI to do console work.

  • Where it applies. Measured on the Codex CLI. The Codex desktop app and the IDE extension read the same settings according to OpenAI's documentation, but haven't been measured yet. This connection does not show up in chatgpt.com web chats.

Full index → Docs View as Markdown