Home / gemachdao / gdex-skill · GitHub

gdex-authentication SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

gdex-authentication from gemachdao/gdex-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add gemachdao/gdex-skill/gdex-authentication@git:20261019.d793ca7

Pins git:20261019.d793ca7 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: gemachdao/gdex-skill
Path: plugins/gdex/skills/gdex-authentication/SKILL.md
Versions recorded: 2
Latest version: git:20261019.d793ca7, committed Oct 19, 2026
First version recorded: Oct 15, 2026
Size: 14,404 bytes
Repository stars: 4
License: MIT

Managed-custody authentication — shared API key login, session keypair generation, encrypted computedData payloads, AES-256-CBC encryption, and secp256k1 trade signing.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# GDEX: Authentication

All GDEX trading uses **managed-custody wallets** with encrypted `computedData` payloads. This skill covers both the simple shared-API-key auth and the full managed-custody flow.

## When to Use

- Setting up authentication for any trading operation
- Implementing managed-custody sign-in for a control wallet
- Understanding the encryption and signing pipeline
- Troubleshooting auth errors (401, 403, code 103)

## Prerequisites

```bash
npm install @gemachdao/gdex-skill
```

## 0. MCP Server: `gdex_connect` (no secrets in chat)

MCP clients do not run this flow by hand. Call `gdex_connect` with a local key file
(`{ keyFile: "~/wallet.json" }`) or `{ create: true }` for a new wallet; the server signs in,
stores the keys under `~/.gdex/accounts` (0600) and returns an `accountRef`. Pass `accountRef`
to every trading tool instead of `apiKey` / `walletAddress` / `sessionPrivateKey` / `data`.
`gdex_accounts` lists connected accounts and `gdex_disconnect` forgets one.

SDK users run the managed-custody sign-in below and pass `apiKey`, `walletAddress`
(the control wallet) and `sessionPrivateKey` to each write call.

## 1. Shared API Key Login (Simple)
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add gemachdao/gdex-skill/gdex-authentication@sha256:ccf2ae0e03a2cf94

The line at the top of this page pins the label git:20261019.d793ca7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_uz3wp53i2lgsq7p3.svg)](https://markdownregistry.com/a/art_uz3wp53i2lgsq7p3)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Oct 15, 2026 and Oct 19, 2026, about one every 4 days.

version	committed	commit	size	audit
git:20261019.d793ca7 latest	2026-10-19	d793ca7	14,404 B	A	view · diff
git:20261015.073f01e	2026-10-15	073f01e	13,623 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (14404 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

gemachdao/gdex-skill · 4 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_uz3wp53i2lgsq7p3
GET https://markdownregistry.com/api/v1/resolve?ref=gemachdao/gdex-skill/gdex-authentication
GET https://markdownregistry.com/api/v1/blob/ccf2ae0e03a2cf94533988307f03f641c5f60626798019c657601051c3ca56cb

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from gemachdao/gdex-skill

gdex-agent-trading SKILL.md skill

gemachdao/gdex-skill · plugins/gdex/skills/gdex-agent-trading/SKILL.md · Default agent flow for trading on GDEX via MCP — status, connect, preview, execute within the user's authority, follow…

git:20261019.d793ca7 · audit A · 4 stars

gdex-bridge SKILL.md skill

gemachdao/gdex-skill · plugins/gdex/skills/gdex-bridge/SKILL.md · Cross-chain bridging — get estimates and execute native token transfers between EVM chains, Solana, and Sui via…