How do I install the Setup skill?

Run npx skillmds@latest add hashgraph-online/setup-5 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

hashgraph-online (@hashgraph-online) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Setup by hashgraph-online — Agent Skill

Name: Setup
Rating: 4.5 (4 reviews)
Author: hashgraph-online

File contents

AgentGuards setup

Guide the user through finishing AgentGuards setup after installing the plugin. The plugin already bundles the MCP server and the enforcing hooks — the only thing the user must supply is their API key.

Steps

Check for the API key. Look for the AGENTGUARDS_API_KEY environment variable. If it is missing or does not start with ag_, tell the user to:
- Get a key from the dashboard at https://agentguards.co/dashboard/keys
- Export it so both the MCP server and the hooks can read it. For the current shell and future sessions, add to their shell profile (~/.bashrc, ~/.zshrc, etc.):
```
export AGENTGUARDS_API_KEY=ag_your_token_here
```
- Restart Codex (or start a new session) so the MCP server and hooks pick up the key from the environment.
Confirm the URL (optional). AgentGuards defaults to https://prod.agentguards.co. Only set AGENTGUARDS_URL if the user runs a self-hosted instance.
Fail-open vs fail-closed. The hooks fail closed by default — if the AgentGuards service is unreachable, actions are blocked. A user who prefers availability over strict enforcement can set AGENTGUARDS_FAIL_OPEN=true. Mention this only if they ask or report unexpected blocks.
Verify. Call the AgentGuards health_check tool from the agentguards MCP server. Report whether the service is reachable and which key prefix is active. If it fails, the most common cause is AGENTGUARDS_API_KEY not being exported in the environment Codex was launched from.
Summarize what is now active: UserPromptSubmit input scanning, PreToolUse shell-command authorization, PostToolUse web-content scanning, and the check_input / authorize_action MCP tools.

Source: hashgraph-online/awesome-codex-plugins → plugins/alelaguard/agentguards-plugins/skills/setup/SKILL.md

---name: setup-5description: Set up and verify AgentGuards in Codex. Use when the user asks to configure AgentGuards, set their API key, or check that the guardrails are wired up correctly.--- # AgentGuards setup Guide the user through finishing AgentGuards setup after installing the plugin. The plugin already bundles the MCP server and the enforcing hooks — the only thing the user must supply is their API key. ## Steps 1. **Check for the API key.** Look for the `AGENTGUARDS_API_KEY` environment variable. If it is missing or does not start with `ag_`, tell the user to: - Get a key from the dashboard at https://agentguards.co/dashboard/keys - Export it so both the MCP server and the hooks can read it. For the current shell and future sessions, add to their shell profile (`~/.bashrc`, `~/.zshrc`, etc.): ``` export AGENTGUARDS_API_KEY=ag_your_token_here ``` - Restart Codex (or start a new session) so the MCP server and hooks pick up the key from the environment. 2. **Confirm the URL (optional).** AgentGuards defaults to `https://prod.agentguards.co`. Only set `AGENTGUARDS_URL` if the user runs a self-hosted instance. 3. **Fail-open vs fail-closed.** The hooks fail **closed** by default — if the AgentGuards service is unreachable, actions are blocked. A user who prefers availability over strict enforcement can set `AGENTGUARDS_FAIL_OPEN=true`. Mention this only if they ask or report unexpected blocks. 4. **Verify.** Call the AgentGuards `health_check` tool from the `agentguards` MCP server. Report whether the service is reachable and which key prefix is active. If it fails, the most common cause is `AGENTGUARDS_API_KEY` not being exported in the environment Codex was launched from. 5. **Summarize what is now active:** UserPromptSubmit input scanning, PreToolUse shell-command authorization, PostToolUse web-content scanning, and the `check_input` / `authorize_action` MCP tools. --- **Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/alelaguard/agentguards-plugins/skills/setup/SKILL.md`

Frequently asked questions

Setup