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.
npx skills add holon-run/uxc --skill bitquery-graphql-skillgit clone --depth 1 https://github.com/holon-run/uxcWrote 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.
[](https://agentmods.dev/skills/holon-run/uxc/bitquery-graphql-skill)<a href="https://agentmods.dev/skills/holon-run/uxc/bitquery-graphql-skill"><img src="https://agentmods.dev/badge/skills/holon-run/uxc/bitquery-graphql-skill/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.
<a href="https://agentmods.dev/skills/holon-run/uxc/bitquery-graphql-skill"><img src="https://agentmods.dev/badge/skills/holon-run/uxc/bitquery-graphql-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 20 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00046 | $0.01733 |
| Opus 5.5 | $0.00018 | $0.00693 |
| Sonnet 5.5 | $0.00009 | $0.00347 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
bitquery-graphql-skill 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bitquery GraphQL Skill
Use this skill to run Bitquery GraphQL API operations through uxc.
Reuse the uxc skill for discovery, GraphQL execution, OAuth lifecycle, and generic error handling.
Prerequisites
uxcis installed and available inPATH.- Network access to
https://streaming.bitquery.io/graphql. - A Bitquery application
client_idandclient_secretare available.
Authentication
Bitquery uses bearer access tokens. The most stable agent path is OAuth client_credentials, not a copied temporary token.
- Create a Bitquery application and note:
- application
client_id - application
client_secret - token scope
api
- application
- Login once with OAuth client credentials:
uxc auth oauth login bitquery-graphql --endpoint https://streaming.bitquery.io/graphql --flow client_credentials --client-id <client_id> --client-secret <client_secret> --scope api --token-endpoint https://oauth2.bitquery.io/oauth2/token- This flow completes in one command. No browser approval page is required.
- Bind the GraphQL endpoint:
uxc auth binding add --id bitquery-graphql --host streaming.bitquery.io --path-prefix /graphql --scheme https --credential bitquery-graphql --priority 100
- Verify auth mapping:
uxc auth binding match https://streaming.bitquery.io/graphqluxc auth oauth info bitquery-graphql
Core Workflow
- Use fixed link command by default:
command -v bitquery-graphql-cli- If missing, create it:
uxc link bitquery-graphql-cli https://streaming.bitquery.io/graphql bitquery-graphql-cli -h- If command conflict is detected and cannot be safely reused, stop and ask skill maintainers to pick another fixed command name.
- Discover available root operations:
bitquery-graphql-cli -h- Verified roots currently include
query/EVM,query/Solana,query/Trading,query/Tron, and matchingsubscription/*roots.
- Inspect a specific operation:
bitquery-graphql-cli query/EVM -hbitquery-graphql-cli query/Trading -h
- Execute with positional JSON and explicit GraphQL selection sets:
bitquery-graphql-cli query/EVM '{"network":"base","dataset":"combined","_select":"DEXTrades(limit: {count: 1}) { Transaction { Hash } }"}'
- Prefer
query/*operations first.uxc subscribenow auto-negotiates moderngraphql-transport-wsand legacygraphql-wscompatibility profiles forsubscription/*.- Live Bitquery subscription validation now succeeds when you provide an explicit
_selectthat matches a stream-friendly entity shape. - Prefer
subscription/EVMas the first validation target rather thansubscription/Trading.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 164 lines · 46 tokens per session scan A 30fe154f472c
bitquery-graphql-skill is a skill published in the GitHub repository holon-run/uxc (119 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,733 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
linear
Linear project management — issues, cycles, and projects via GraphQL API.
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
pipefy-api-fallback
Use this skill when a toolkit operation fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow…
spotify
Spotify API integration — playback control, playlists, search, recommendations.
youtube-content
YouTube Data API — search, video details, channel info, transcripts.