Agent skill

Quicknode Security Basics

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Harden QuickNode endpoints with server-side token handling, separate credentials, least-privilege account roles, and plan-appropriate security filters.

MITAuto-check passedBackend & APIs

Install Quicknode Security Basics

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill quicknode-security-basics -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace quicknode-security-basics --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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/quicknode-security-basics .claude/skills/quicknode-security-basics && 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
quicknode-security-basics
GitHub stars
2.8k
Token cost
~1k tokens
SKILL.md length
409 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Harden QuickNode endpoints with server-side token handling, separate credentials, least-privilege account roles, and plan-appropriate security filters.

  • Works in 6 steps: Find exposure → Separate identities → Choose layered controls → …
  • Reviewing exposure
  • SKILL.md covers Overview, Prerequisites, Instructions and Tool Discipline, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Quicknode Security Basics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Harden QuickNode endpoints with server-side token handling, separate credentials, least-privilege account roles, and plan-appropriate security filters. Use when reviewing exposure, isolating applications, or responding to a leaked endpoint. Trigger with: "secure QuickNode", "harden a QuickNode endpoint", "rotate a leaked QuickNode token".

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: JWT, referrer allowlists, domain masking, and advanced rate controls can be plan-specific

It sits in Backend & APIs, covering Backend development. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Reviewing exposure
  • Isolating applications
  • Responding to a leaked endpoint
  • With: secure QuickNode

Example prompts

  • “secure QuickNode”
  • “harden a QuickNode endpoint”
  • “rotate a leaked QuickNode token”
  • “/quicknode-security-basics”

Requirements

  • Compatibility (from SKILL.md): JWT, referrer allowlists, domain masking, and advanced rate controls can be plan-specific
  • Pre-approved tools (allowed-tools): Read, Grep, Write, Edit, Bash(qn:*)

Workflow steps

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

  1. Find exposure
  2. Separate identities
  3. Choose layered controls
  4. Keep privileged calls server-side
  5. Inspect configuration
  6. Exercise response

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Write
    • Edit
    • Bash(qn:*)

    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

    Links to these hosts (documentation or services it may open):

    • quicknode.com

    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.

  • Compatibility

    JWT, referrer allowlists, domain masking, and advanced rate controls can be plan-specific

    From compatibility in the SKILL.md frontmatter.

Context cost

Quicknode Security Basics loads about 1k tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 409 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~92
When it runs · the whole SKILL.md, loaded when a task matches
~1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

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 jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 409 words, ~1,032 tokens.

Download SKILL.mdSave it as .claude/skills/quicknode-security-basics/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
quicknode-security-basics
description
Harden QuickNode endpoints with server-side token handling, separate credentials, least-privilege account roles, and plan-appropriate security filters. Use when reviewing exposure, isolating applications, or responding to a leaked endpoint. Trigger with: "secure QuickNode", "harden a QuickNode endpoint", "rotate a leaked QuickNode token".
allowed-tools
Read, Grep, Write, Edit, Bash(qn:*)
compatibility
JWT, referrer allowlists, domain masking, and advanced rate controls can be plan-specific
version
2.0.0
argument-hint
[endpoint-and-threat-model]
model
inherit
effort
high
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, quicknode, security, authentication, hardening

QuickNode Endpoint Hardening

Overview

Protect endpoint tokens as credentials, isolate consumers with multiple tokens, and layer only controls that match the client threat model. A browser referrer rule is not a substitute for keeping privileged RPC or account keys on a server.

Prerequisites

  • Endpoint inventory with owners, applications, and environments
  • Current plan and available endpoint-security controls
  • A threat model covering browser, server, CI, and operator access

Instructions

Step 1: Find exposure

Use Read and Grep for quiknode.pro, x-token, x-api-key, JWT configuration, logs, examples, and client bundles. Stop and rotate any live credential committed to Git or shipped to an untrusted client.

Step 2: Separate identities

Create distinct endpoint tokens for applications and environments. Keep Admin API/SDK API keys separate from chain RPC tokens. Apply least-privilege team and account roles.

Step 3: Choose layered controls

Use token authentication for every endpoint. Add JWT for short-lived server authorization when supported, referrer allowlists for browser-origin reduction, and IP or method limits for known traffic patterns. Document plan dependencies.

Step 4: Keep privileged calls server-side

Use Write or Edit to route transaction submission, archive/debug methods, and account-control calls through a trusted backend. Do not embed endpoint or API tokens in public JavaScript.

Step 5: Inspect configuration

Use Bash(qn:*) to read endpoint security state with an approved authenticated operator identity. Compare actual tokens, filters, limits, domains, and team access to the declared policy without printing secret values.

Show full SKILL.md (177 more words)Show less
Step 6: Exercise response

Prove that an unauthorized origin, token, method, or IP is rejected as designed. Revoke one test token and confirm other isolated consumers continue. Record recovery time and escalation owner.

Tool Discipline

Use Read and Grep for exposure discovery, Write/Edit for server-side boundaries and policy, and Bash(qn:*) for read-only security inspection. Credential creation, revocation, and production filter changes require an explicit checkpoint.

Output

  • Endpoint threat model and credential map
  • Actual-versus-declared security control comparison
  • Negative authorization tests
  • Rotation and incident-response procedure

Examples

A public dApp calls a backend that holds the endpoint token. Production and staging use separate tokens, and a method limit prevents the public route from invoking debug methods.

Error Handling

FailureResponse
Token exposedRevoke, replace, sanitize history and logs, then investigate use
Referrer rule blocks valid trafficRoll back the specific rule; do not expose the token
-32611 rejectionCompare method and filter policy before retrying
Security feature unavailableRecord the plan gap and enforce the boundary in the application

Resources

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

Files

SKILL.md and 1 other file (references) in skills/.curated/quicknode-security-basics of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit 80f86df

Compare with similar skills

Quicknode Security Basics 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.

Quicknode Security Basics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quicknode Security Basics this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1kAutomated safety check: PassMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
Fortify Developmentcoollabsio/coolify63k4 repos~1.9kAutomated safety check: PassMIT
Node Backend Development Guidelinesdiet103/claude-code-infrastructure-showcase10k2 repos~2kAutomated safety check: PassMIT
Laravel Best Practicesanonaddy/anonaddy4.9k13 repos~1.2kAutomated safety check: PassMIT
Laravel Actionscoollabsio/coolify63k—~2.4kAutomated safety check: PassApache-2.0

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed
  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed
  • Node Backend Development Guidelines

    diet103/claude-code-infrastructure-showcase

    Sets layered architecture and coding rules for Node.js, Express and TypeScript microservices, covering routes, controllers, services, repositories, Prisma, Sentry and Zod.

    10k GitHub starsUsed in 2 repos~2k tokens
    Backend & APIsAuto-check passed
  • Laravel Best Practices

    anonaddy/anonaddy

    Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code.

    4.9k GitHub starsUsed in 13 repos~1.2k tokens
    Backend & APIsAuto-check passed
  • Laravel Actions

    coollabsio/coolify

    Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions.

    63k GitHub stars~2.4k tokensUpdated today
    Backend & APIsAuto-check passed
  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    162 GitHub starsUsed in 18 repos~4k tokens
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Quicknode Security Basics

What does Quicknode Security Basics do?

Harden QuickNode endpoints with server-side token handling, separate credentials, least-privilege account roles, and plan-appropriate security filters. Quicknode Security Basics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Harden QuickNode endpoints with server-side token handling, separate credentials, least-privilege account roles, and plan-appropriate security filters.

When should I use Quicknode Security Basics?

Quicknode Security Basics fits situations like: reviewing exposure; isolating applications; responding to a leaked endpoint; with: secure QuickNode.

How do I install Quicknode Security Basics in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill quicknode-security-basics -a claude-code`. Or copy the skill folder (skills/.curated/quicknode-security-basics in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/quicknode-security-basics in your project. Claude Code loads it when a task matches its description.

How do I install Quicknode Security Basics in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill quicknode-security-basics -a codex`. Or copy the skill folder (skills/.curated/quicknode-security-basics in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/quicknode-security-basics in your project. Codex loads it when a task matches its description.

Can I use Quicknode Security Basics 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 jeremylongshore/tons-of-skills-marketplace --skill quicknode-security-basics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quicknode-security-basics, .gemini/skills/quicknode-security-basics, .github/skills/quicknode-security-basics and .opencode/skills/quicknode-security-basics in your project.

What does Quicknode Security Basics need to run?

SKILL.md names no scripts, command-line tools or credentials: Quicknode Security Basics is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Write, Edit, Bash(qn:*). Compatibility (from SKILL.md): JWT, referrer allowlists, domain masking, and advanced rate controls can be plan-specific.

Does Quicknode Security Basics access the network?

SKILL.md names 1 domain. As links in the text: quicknode.com. This is read from the text; nothing was executed.

Is Quicknode Security Basics 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 Quicknode Security Basics use?

Quicknode Security Basics 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 Quicknode Security Basics use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 176 tokens, read only when the agent opens those files.

What are the alternatives to Quicknode Security Basics?

Skills that share tags, products or a category with Quicknode Security Basics: Configuring Horizon (coollabsio/coolify, 63k stars), Fortify Development (coollabsio/coolify, 63k stars), Node Backend Development Guidelines (diet103/claude-code-infrastructure-showcase, 10k stars) and Laravel Best Practices (anonaddy/anonaddy, 4.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quicknode Security Basics?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.