New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Qatom

by hashgraph-online in hashgraph-online/awesome-codex-plugins

Use and publish Qatom marketplace tools. An agent skill from hashgraph-online/awesome-codex-plugins.

MITAuto-check passedBackend & APIs

Install Qatom

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill qatom -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins qatom --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/TODAQmicro/qatom-skill/skills/qatom .claude/skills/qatom && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
qatom
GitHub stars
1.2k
Token cost
~3k tokens
SKILL.md length
1,518 words
Files
1
Skills in repo
686
Repo updated
First seen
Licence
MIT

At a glance

Use and publish Qatom marketplace tools. An agent skill from hashgraph-online/awesome-codex-plugins.

  • Works in 4 steps: Create a Provider Twin → Configure the Twin → Register the Tool → …
  • : calling paywalled API tools from the Qatom marketplace
  • SKILL.md covers When to Use, Connecting, Auth Flow and Available Tools, plus 3 more sections
  • Reaches mcp.m.todaq.net and load.m.todaq.net

What it does

Qatom is an agent skill from hashgraph-online/awesome-codex-plugins. Use and publish Qatom marketplace tools. Use when: calling paywalled API tools from the Qatom marketplace, checking wallet balance, managing your agent twin wallet, or helping a user register as a Qatom provider to earn per-call payments from their own tools. Connects to the hosted Qatom MCP server at mcp.m.todaq.net via Qatom OIDC. NOT for: direct payment API calls or free tools.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering OAuth and OpenID Connect and MCP servers. It works with Model Context Protocol. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is MIT.

When your agent uses it

  • : calling paywalled API tools from the Qatom marketplace
  • Checking wallet balance
  • Managing your agent twin wallet
  • Helping a user register as a Qatom provider to earn per-call payments from their own tools

Example prompts

  • “/qatom”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Create a Provider Twin
  2. Configure the Twin
  3. Register the Tool
  4. Test Your Tool

What it can do on your machine

Read from SKILL.md and the folder at commit 78497e5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • mcp.m.todaq.net
    • load.m.todaq.net
    • pay.m.todaq.net

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Qatom loads about 3k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 1,518 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 78497e5, republished under its MIT licence (© hashgraph-online). 1,518 words, ~3,024 tokens.

Download SKILL.mdSave it as .claude/skills/qatom/SKILL.md (or your agent's skills folder).
name
qatom
description
Use and publish Qatom marketplace tools. Use when: calling paywalled API tools from the Qatom marketplace, checking wallet balance, managing your agent twin wallet, or helping a user register as a Qatom provider to earn per-call payments from their own tools. Connects to the hosted Qatom MCP server at mcp.m.todaq.net via Qatom OIDC. NOT for: direct payment API calls or free tools.
homepage
https://github.com/todaqmicro/qatom-skill
license
MIT

Qatom Marketplace Skill

Access paywalled API tools from the Qatom marketplace. An agent (sandbox) twin wallet handles payments transparently, so no manual approval steps interrupt your workflow. Providers can register their own APIs and earn per-call revenue automatically.

When to Use

✅ USE this skill when:

  • User asks to call a tool from the Qatom marketplace
  • A tool requires Qatom wallet payment
  • Checking wallet balance or twin info
  • Managing your agent (sandbox) twin wallet, funding, or transfers
  • Registering as a Qatom provider to earn per-call revenue from your tools
  • Managing provider twins, configuring upstream APIs, or updating registered tools

❌ DON'T use this skill when:

  • User wants to interact with the payment API directly
  • Tool is free and doesn't require a wallet

Connecting

The Qatom MCP server is hosted at https://mcp.m.todaq.net. Connect using any MCP-compatible client with OAuth 2.0 support.

claude.ai (built-in OAuth): Add https://mcp.m.todaq.net as a remote MCP server. The platform handles OAuth redirect and token management automatically.

Claude Desktop: Add the server to your claude_desktop_config.json with OAuth configuration. The desktop client will open your browser for the Qatom OIDC login flow and store the resulting token.

Other MCP clients: Connect to https://mcp.m.todaq.net using standard OAuth 2.0. The authorization server is at https://pay.m.todaq.net. Request the twin scope to receive agent twin credentials alongside your access token.

After connecting, all available Qatom tools appear in the client's tool list automatically.

Auth Flow

  1. OAuth redirect — MCP client redirects to Qatom OIDC login at pay.m.todaq.net
  2. User authenticates — email + 2FA (TOTP) via the Qatom Flutter app or web
  3. Twin auto-provisioning — OIDC returns user identity including twin_hostname and agent_twin_hostname + agent_twin_key. The agent twin is a sandbox wallet auto-provisioned for MCP use. If no agent twin exists, one is created during the first connection.
  4. Token introspection — every tool call validates the Bearer token against the OIDC introspection endpoint (result cached for 60 seconds)
  5. Session persistence — tokens stored by the MCP client persist across tool calls and sessions, so re-auth is rare
  6. MFA skipped for Bearer — agent-initiated calls use a Bearer token (service-to-service). The paywall skips MFA entirely for Bearer calls, so payments execute immediately without manual approval

Available Tools

Wallet Tools

These 4 tools are always available and manage your TODAQ wallet:

ToolDescription
agent_wallet_infoGet your TODAQ twin hostname and current USD TDN balances. No input required — uses your authenticated session.
check_wallet_balanceGet all your TODAQ twins and their current USD TDN balances. No input required — uses your authenticated session.
fund_agent_walletGet the URL to add funds to your primary wallet via the web UI. Only use this when the primary wallet has insufficient balance to transfer to the agent wallet. After adding funds, use transfer_to_agent_wallet to move them to the agent wallet. The chargeup URL is https://load.m.todaq.net.
transfer_to_agent_walletTransfer USD TDN balance from your primary wallet to your agent (sandbox) wallet. Only call this when explicitly requested by the user.
Dynamic Tools

Additional tools appear dynamically from the marketplace catalog, fetched from the payment API at connection time (cached for 60 seconds). The agent sees them alongside the static wallet tools in its tool list. Tool names use snake_case (e.g., "Current Weather" registers as current_weather).

Provider Admin Tools

These 8 tools let you create and manage provider twins, register API tools in the marketplace, and earn per-call revenue:

ToolDescription
twin_statusGet the status and balances of your provider twins used for receiving payments. Use this to check if you have a provider twin and what its hostname is.
create_twinCreate a new provider twin to receive payments for your APIs. Providers can have multiple twins.
configure_twinLink your provider twin to the real upstream API it will proxy to, and set your price per call.
register_toolRegister a new API tool in the marketplace. Run configure_twin first to set up your provider twin, then provide the tool details here. The service URL is derived automatically from your twin hostname.
list_my_toolsList all dynamic tools you have registered in the marketplace.
update_toolUpdate an existing dynamic tool in the marketplace.
deactivate_toolDeactivate a tool from the marketplace. It will be hidden from consumers immediately (note: MCP agent discovery catalogs cache for 60 seconds).
test_toolTest a dynamic tool you created by executing it through the paywall exactly as a consumer would. Note: Your agent sandbox twin will pay your provider twin for this test call.

Payment Flow

When an agent calls a marketplace tool, the MCP server orchestrates payment transparently:

  1. Token validation — MCP server validates the Bearer token via OIDC introspection. Identifies the user's agent twin for payment.
  2. Bearer skips MFA — Bearer token calls bypass MFA entirely. Payment executes immediately.
  3. Paywall request — MCP server POSTs to /v4/paywall on the payment API with:
    • amount — the tool's price in USD TDN
    • serviceUrl — the upstream API URL
    • serviceMethod — GET, POST, or PUT
    • additionalParams — tool arguments, present only for POST/PUT tools
  4. GET tools — arguments are injected as query string parameters on serviceUrl. No additionalParams field in the paywall body.
  5. POST/PUT tools — arguments are packed into the additionalParams field and forwarded as the request body to the upstream API.
  6. TODA protocol payment — the payment API calls the agent twin node directly. The agent twin transfers the tool's price to the provider twin via the TODA protocol.
  7. Upstream proxy — the provider twin proxies the request to the upstream service URL. The response flows back through the provider twin → payment API → MCP server → agent.
  8. Response delivered — the agent receives the upstream API response as the tool call result.
Show full SKILL.md (598 more words)Show less

Agent Twin Wallet

Every MCP-authenticated user gets an agent (sandbox) twin, separate from their primary human wallet. This twin is auto-provisioned during the first OAuth connection and is used exclusively for agent-initiated marketplace payments.

Primary vs Sandbox Twin
Primary TwinAgent (Sandbox) Twin
PurposeYour main wallet, controlled via the Qatom Flutter appDedicated wallet for agent marketplace spending
ProvisioningCreated when you register your Qatom accountAuto-provisioned on first MCP connection
Keytwin_hostname + twin_keyagent_twin_hostname + agent_twin_key
ControlHuman-managed (Flutter app, web UI)Agent-managed (MCP tool calls only)
SpendingManual, MFA-gatedAutomatic, no MFA (Bearer token flow)
Fund → Transfer → Spend Lifecycle
1. FUND       Primary wallet gets TDN
                → Use fund_agent_wallet to get the chargeup URL (https://load.m.todaq.net)
                → Add funds through the web UI
                ↓
2. TRANSFER   Move TDN from primary to agent sandbox wallet
                → Use transfer_to_agent_wallet with amount and dq_type
                → Only do this when the agent wallet balance is too low
                ↓
3. SPEND      Agent calls marketplace tools
                → Each call deducts the tool's price from the agent sandbox twin
                → Payment goes to the provider twin automatically
Edge Cases
  • Pre-existing sessions — sessions created before agent twin auto-provisioning may have agentTwinHostname as undefined. The MCP server falls back to the primary twinHostname in this case. On the next tool call, the token is re-validated and the agent twin claims are restored automatically.
  • Token expiry — OAuth tokens expire after a set duration. When this happens, the MCP client re-authenticates and agent twin claims are refreshed. Wallet balances and twin hostnames remain stable across token refreshes.
  • Insufficient sandbox balance — if the agent twin lacks funds for a tool call, the paywall returns an error. The agent should tell the user to add funds and use transfer_to_agent_wallet before retrying.

Become a Qatom Provider

Register your own API endpoints as marketplace tools and earn per-call revenue. Payments flow via TODA protocol from consumer agent twins to your provider twin, with no manual invoicing or settlement.

Just tell your agent: "Help me register as a Qatom provider." The agent will walk you through these steps using the provider admin tools:

Step 1 — Create a Provider Twin

The agent calls create_twin, which provisions a new provider twin to receive payments. Providers can have multiple twins, each linked to a different upstream API or pricing tier. The twin hostname is returned and used in the next steps.

Step 2 — Configure the Twin

The agent calls configure_twin with three parameters:

  • hostname — your provider twin hostname (from step 1 or twin_status)
  • target_url — the real upstream API URL (must use https)
  • price_per_call — minimum USD TDN charged per call

This links your provider twin to the upstream API it will proxy traffic to.

Step 3 — Register the Tool

The agent calls register_tool to list your API in the marketplace. Required parameters:

  • twin_hostname — your provider twin hostname
  • name — tool name in snake_case (e.g., get_weather_current)
  • description — what the tool does, shown to AI agents during discovery
  • provider — your display name shown in the marketplace
  • price_per_call — price per call in USD TDN (should match configure_twin)
  • service_method — GET, POST, or PUT (the HTTP method your upstream API expects)
  • input_schema — JSON Schema object describing the parameters consumers must pass

The service URL is derived automatically from your twin hostname.

Step 4 — Test Your Tool

The agent calls test_tool with your tool's ID and sample arguments. This executes the tool through the full paywall exactly as a consumer would experience it. Your agent sandbox twin pays your provider twin for this test call, so you can verify the end-to-end flow including payment.

After testing, your tool is live in the marketplace. Any authenticated MCP agent can discover and call it. The catalog refreshes every 60 seconds, so new tools are visible almost immediately.

Managing Your Tools

Once registered, you can use the provider admin tools to manage your marketplace presence:

  • list_my_tools — see all your registered tools with their IDs
  • update_tool — change name, description, price, or toggle active/inactive
  • deactivate_tool — hide a tool from consumers (visible in the catalog within 60 seconds)
  • twin_status — check provider twin balances (the TDN you've earned from tool calls)

© hashgraph-online, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/TODAQmicro/qatom-skill/skills/qatom of hashgraph-online/awesome-codex-plugins.

Open the folder on GitHubat commit 78497e5

Compare with similar skills

Qatom next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Qatom compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qatom this skillhashgraph-online/awesome-codex-plugins1.2k—~3kAutomated safety check: PassMIT
Xquik MCPXquik-dev/x-twitter-scraper2091 repos~997Automated safety check: PassMIT
MCP Dart Streamable HTTPleehack/mcp_dart116—~2kAutomated safety check: PassMIT
Unifapiunifapi-agent/agents587—~741Automated safety check: PassMIT
E2a Setuptokencanopy/e2a192—~820Automated safety check: PassApache-2.0
MCP OAuth Remote GatewayLuciole-Studio/Misaka-Agent1391 repos~6kAutomated safety check: NotesMIT

Similar skills

  • Xquik MCP

    Xquik-dev/x-twitter-scraper

    Connect, verify, and troubleshoot Xquik's remote MCP server.

    209 GitHub starsUsed in 1 repo~997 tokens
    Backend & APIsAuto-check passed

  • MCP Dart Streamable HTTP

    leehack/mcp_dart

    A skill your agent uses when serving an MCP server over HTTP with mcpdart or connecting to a remote one: StreamableMcpServer setup, Host and Origin allowlists (DNS rebinding protection), CORS for…

    116 GitHub stars~2k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

  • Unifapi

    unifapi-agent/agents

    A skill your agent uses when working with UnifAPI public-data APIs or the UnifAPI MCP server: connecting OAuth MCP clients, discovering operations, calling social/search/scrape/news APIs…

    587 GitHub stars~741 tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • E2a Setup

    tokencanopy/e2a

    A skill your agent uses when a user wants to connect or authorize the e2a MCP server, select or create an agent inbox, verify first-run readiness, or set up a custom email domain.

    192 GitHub stars~820 tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

  • MCP OAuth Remote Gateway

    Luciole-Studio/Misaka-Agent

    Manual OAuth for remote MCP servers on headless gateways. An agent skill from Luciole-Studio/Misaka-Agent.

    139 GitHub starsUsed in 1 repo~6k tokens
    Backend & APIsAuto-check: notes

  • Vercel Connect

    vercel/vercel-plugin

    Official

    Vercel Connect expert guidance for securely obtaining scoped credentials for third-party services on behalf of apps or users.

    301 GitHub stars~5.3k tokensUpdated today
    Backend & APIsAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 686 skills in this repo

  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.2k GitHub stars~922 tokensUpdated today
    Auto-check passed

  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.2k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.2k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.2k GitHub stars~618 tokensUpdated today
    Auto-check passed

  • Manuscript Engagement Analytics

    hashgraph-online/awesome-codex-plugins

    Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and…

    1.2k GitHub stars~875 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Qatom

What does Qatom do?

Use and publish Qatom marketplace tools. An agent skill from hashgraph-online/awesome-codex-plugins. Qatom is an agent skill from hashgraph-online/awesome-codex-plugins. Use and publish Qatom marketplace tools.

When should I use Qatom?

Qatom fits situations like: : calling paywalled API tools from the Qatom marketplace; checking wallet balance; managing your agent twin wallet; helping a user register as a Qatom provider to earn per-call payments from their own tools.

How do I install Qatom in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill qatom -a claude-code`. Or copy the skill folder (plugins/TODAQmicro/qatom-skill/skills/qatom in hashgraph-online/awesome-codex-plugins) into .claude/skills/qatom in your project. Claude Code loads it when a task matches its description.

How do I install Qatom in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill qatom -a codex`. Or copy the skill folder (plugins/TODAQmicro/qatom-skill/skills/qatom in hashgraph-online/awesome-codex-plugins) into .agents/skills/qatom in your project. Codex loads it when a task matches its description.

Can I use Qatom in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill qatom -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qatom, .gemini/skills/qatom, .github/skills/qatom and .opencode/skills/qatom in your project.

What does Qatom need to run?

SKILL.md names no scripts, command-line tools or credentials: Qatom is instructions for the agent only.

Does Qatom access the network?

SKILL.md names 3 domains. In commands or code: mcp.m.todaq.net, load.m.todaq.net and pay.m.todaq.net; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Qatom safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Qatom use?

Qatom is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Qatom use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Qatom?

Skills that share tags, products or a category with Qatom: Xquik MCP (Xquik-dev/x-twitter-scraper, 209 stars), MCP Dart Streamable HTTP (leehack/mcp_dart, 116 stars), Unifapi (unifapi-agent/agents, 587 stars) and E2a Setup (tokencanopy/e2a, 192 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qatom?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,242 GitHub stars. The repository holds 686 skills in this directory. The repository was last updated on October 8, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.