qubiton-status

qubiton-status is a skill for Claude Code, Codex from qubitonhq/qubiton-cursor-plugin. It costs 80 tokens per session (1,016 once invoked), scanned A, original, MIT.

A QubitOn connection checker for testing access to tax-validation tools and seeing which countries and tax-ID formats are supported.

In plain words
What is it for?
It checks the available QubitOn tools, runs a basic validation, reports connection status, and interprets common error codes.
Why use it?
It helps explain whether QubitOn is connected, whether its API key works, and why a tool call failed. Usage and billing details are handled in the QubitOn dashboard.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It checks the available QubitOn tools, runs a basic validation, reports connection status, and interprets common error codes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/qubitonhq/qubiton-cursor-plugin/qubiton-status
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add qubitonhq/qubiton-cursor-plugin --skill qubiton-status
Clone the repo
git clone --depth 1 https://github.com/qubitonhq/qubiton-cursor-plugin

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for qubiton-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/qubitonhq/qubiton-cursor-plugin/qubiton-status/github.svg)](https://agentmods.dev/skills/qubitonhq/qubiton-cursor-plugin/qubiton-status)
Your own site
<a href="https://agentmods.dev/skills/qubitonhq/qubiton-cursor-plugin/qubiton-status"><img src="https://agentmods.dev/badge/skills/qubitonhq/qubiton-cursor-plugin/qubiton-status/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for qubiton-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/qubitonhq/qubiton-cursor-plugin/qubiton-status"><img src="https://agentmods.dev/badge/skills/qubitonhq/qubiton-cursor-plugin/qubiton-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,016 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00080 $0.01016
Opus 5 $0.00040 $0.00508
Sonnet 5 $0.00016 $0.00203
Haiku 4.5 $0.00008 $0.00102

Measured 8d ago against content hash 72cff17803fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

qubiton-status scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/qubiton/skills/qubiton-status/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

QubitOn status

Two modes: health check and coverage. Plan and quota info are managed in the QubitOn dashboard, not in the MCP server — redirect the user there when they ask about usage or billing.

Mode 1: Health check

User asked whether QubitOn is working, or reported that a tool call failed.

  1. List the QubitOn MCP tools available in the current session.
  2. Interpret:
    • No QubitOn tools at all → "QubitOn MCP isn't connected. Let's run the qubiton-setup skill." Stop.
    • Tools available → run a cheap validation against a known-good input to confirm the API key is accepted. Good choices:
      • ValidateTaxFormat on a well-formed number (doesn't consume quota in the same way as live authority validation)
      • GetSupportedTaxFormats (metadata-only)
  3. Report:
    • ✅ Connected / ⚠️ Connected but key rejected (401) / ❌ Not connected
    • Number of QubitOn tools available in the session
    • Endpoint: https://mcp.qubiton.com/mcp

Error code cheat sheet

When diagnosing a failed call, match the error status:

Status Meaning What to do
401 API key missing or invalid Re-run qubiton-setup Step 2
403 Tool not included in the user's plan Direct them to qubiton.com/pricing
404 Country or variant not supported for that tool Run Mode 2 (coverage) below
429 Rate limit or quota exhausted Check the Retry-After header; for quota, direct them to the Dashboard → Usage
5xx Transient QubitOn service error Retry once with backoff; if persistent, ask the user to contact [email protected]

Mode 2: Coverage

User asked whether a specific country, data type, or tax variant is supported.

Tax coverage — use the MCP server

QubitOn exposes a dedicated tool for tax coverage: GetSupportedTaxFormats. Call it and filter the response:

  • By country (ISO2) — show all tax types that country supports.
  • By tax type — show all countries that have that tax type.
  • Distinguish format-only vs live authority-backed validation in the output; only some countries have live authority connections (e.g., EU VIES, UK HMRC, India GSTIN).

Read the full file on GitHub · 89 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 89 lines · 80 tokens per session scan A 72cff17803fd

Subscribe to this mod's changes

qubiton-status is a skill published in the GitHub repository qubitonhq/qubiton-cursor-plugin (5 stars, last pushed 4mo ago), licensed MIT. It adds 80 tokens to every session and 1,016 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

skillnote-doctor

A diagnostic tool for OpenClaw agents -- checks skill registry connectivity, AGENTS.md setup, config file validity, and installed skill health. Use when your setup seems broken, skills aren't loading, or you want to audit your agent's configuration.

luna-prompts/skillnote · 54 tokens

chatcrystal-debug-recall

Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.

ZengLiangYi/ChatCrystal · 54 tokens

megalinter-check

Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…

ulises-jeremias/agent-toolkit · 96 tokens

megalinter-setup

Install or upgrade MegaLinter on a repository. Use when the user wants to add MegaLinter to a project, set up linting CI, update MegaLinter configuration or version, or says "install megalinter", "setup linting", "add code quality checks". Always goes through npx mega-linter-runner (--install or --upgrade), then…

ulises-jeremias/agent-toolkit · 88 tokens

chrome-devtools

Use Chrome DevTools MCP to control and inspect a live Chrome instance for network, console, performance, rendering, and Deep debugging. Pairs with playwright-cli (deterministic interaction/E2E) — complements, not duplicates.

ulises-jeremias/agent-toolkit · 50 tokens

gh-fix-ci

Diagnose failing GitHub Actions checks on a PR via gh, summarize the failure context, propose a plan, and only implement after explicit user approval. External CI providers (Buildkite, CircleCI, etc.) are reported by URL only.

ulises-jeremias/agent-toolkit · 53 tokens