add-resource

add-resource is a skill for Claude Code from cyanheads/ntfy-mcp-server. It costs 32 tokens per session (2,644 once invoked), scanned A, a copy of add-resource, Apache-2.0.

A scaffold for adding an MCP resource, which is a readable endpoint that exposes data through a URI.

In plain words
What is it for?
Use it when exposing data through a new URI, defining its parameters and data shape, and registering it with an MCP server.
Why use it?
It gives a project a consistent way to add resources while checking that agents can also reach the same data through tools.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the ntfy-mcp-server plugin — 32 skills, 1 MCP server shipped together

Good fit Use it when exposing data through a new URI, defining its parameters and data shape, and registering it with an MCP server.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cyanheads/ntfy-mcp-server/add-resource
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 cyanheads/ntfy-mcp-server --skill add-resource
Clone the repo
git clone --depth 1 https://github.com/cyanheads/ntfy-mcp-server

Made for: Claude Code.

Or install ntfy-mcp-server, the plugin that ships this one along with the rest of its 32 skills, 1 MCP server.

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 add-resource

README.md
[![agentmods](https://agentmods.dev/badge/skills/cyanheads/ntfy-mcp-server/add-resource/github.svg)](https://agentmods.dev/skills/cyanheads/ntfy-mcp-server/add-resource)
Your own site
<a href="https://agentmods.dev/skills/cyanheads/ntfy-mcp-server/add-resource"><img src="https://agentmods.dev/badge/skills/cyanheads/ntfy-mcp-server/add-resource/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 add-resource

Your own site · 80×15
<a href="https://agentmods.dev/skills/cyanheads/ntfy-mcp-server/add-resource"><img src="https://agentmods.dev/badge/skills/cyanheads/ntfy-mcp-server/add-resource.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,644 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 100% copy Near-identical to another mod 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.00032 $0.02644
Opus 5 $0.00016 $0.01322
Sonnet 5 $0.00006 $0.00529
Haiku 4.5 $0.00003 $0.00264

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

Security

Grade A, and why

add-resource 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 10d 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.

Origin

This is a copy

100% identical to add-resource — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/add-resource/SKILL.md · 226 lines

How it starts

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

Context

Resources use the resource() builder from @cyanheads/mcp-ts-core. Each resource lives in src/mcp-server/resources/definitions/ with a .resource.ts suffix. The standard registration pattern uses a definitions/index.ts barrel that collects all resources into an allResourceDefinitions array for createApp(). Fresh scaffolds start with direct imports in src/index.ts — the barrel is introduced as definitions grow. Match the pattern already used by the project you're editing.

Tool coverage. Not all MCP clients expose resources — many are tool-only (Claude Code, Cursor, most chat UIs). Before adding a resource, verify the same data is reachable via the tool surface — either through a dedicated tool, included in another tool's output, or bundled into a broader tool. A resource whose data has no tool path is invisible to a large share of agents.

Steps

  1. Gather the resource's URI template, purpose, and data shape from the user's request — ask only if genuinely absent
  2. Design the URI — use {paramName} for path parameters (e.g., myscheme://{itemId}/data)
  3. Create the file at src/mcp-server/resources/definitions/{{resource-name}}.resource.ts
  4. Register the resource in the project's existing createApp() resource list (directly in src/index.ts for fresh scaffolds, or via a barrel if the repo already has one)
  5. Run bun run devcheck to verify
  6. Smoke-test with bun run rebuild && bun run start:stdio (or start:http)

Template

/**
 * @fileoverview {{RESOURCE_DESCRIPTION}}
 * @module mcp-server/resources/definitions/{{RESOURCE_NAME}}
 */

import { resource, z } from '@cyanheads/mcp-ts-core';

export const {{RESOURCE_EXPORT}} = resource('{{scheme}}://{{{paramName}}}/data', {
  description: '{{RESOURCE_DESCRIPTION}}',
  mimeType: 'application/json',
  // size: 1024,  // optional: content size in bytes, if known
  params: z.object({
    {{paramName}}: z.string().describe('{{PARAM_DESCRIPTION}}'),
  }),
  // auth: ['resource:{{resource_name}}:read'],

  async handler(params, ctx) {
    ctx.log.debug('Fetching resource', { {{paramName}}: params.{{paramName}} });
    // Pure logic — throw on failure, no try/catch
    return { /* resource data */ };
  },

  list: async (extra) => ({
    resources: [
      {
        uri: '{{scheme}}://all',
        name: '{{RESOURCE_LIST_NAME}}',
        mimeType: 'application/json',
      },
    ],
  }),
});

Read the full file on GitHub · 226 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. 10d ago First seen · 226 lines · 32 tokens per session scan A bd2b36cc23dc

Subscribe to this mod's changes

add-resource is a skill published in the GitHub repository cyanheads/ntfy-mcp-server (20 stars, last pushed 6d ago), licensed Apache-2.0. It adds 32 tokens to every session and 2,644 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to add-resource, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

add-provider

Add a new storage or service provider to the core package. Use when implementing a new backend for StorageService (e.g., a new database) or a new service provider (e.g., a new LLM backend).

cyanheads/mcp-ts-core · 47 tokens

blazemeter-api-monitoring

Comprehensive guide for BlazeMeter API Monitoring, including test creation, configuration, scripting, integrations, notifications, and management. Use when working with API Monitoring tests for (1) Creating and configuring API tests, (2) Writing custom scripts (Initial, Pre-request, Post-response), (3) Integrating…

Blazemeter/bzm-mcp · 142 tokens

diagnose-connectivity

Work out why a 3x-ui client cannot connect, in the order that finds the cause fastest — scope the outage, check the core, the inbound, the client's own limits, routing and outbounds, then the node. Use whenever someone reports "it stopped working", a client cannot connect, a site is unreachable through the proxy, or…

pyworkload/3x-ui-mcp · 83 tokens

aurora-backend-setup

Set up, build, or troubleshoot the AURORA Agent (bioprism) MCP server used by the aurora-backend plugin. Use when the aurora-agent MCP server fails to start, when its tools are missing from a session, when asked to install or build the aurora-agent backend, or when a bioprism build or test behaves strangely on Windows.

AURORA-NEURO/aurora-agent · 82 tokens

spotify-exhaustive-feature-sweep

Exhaustive feature sweep across Spotify domains — enumerate all endpoints into quantity-first tool proposals with quota flags and batched GitHub logging.

NovaLux12/spotify-mcp-server · 34 tokens

building-mcp-servers

Use this skill whenever the user wants to design, build, harden, review, or debug an MCP (Model Context Protocol) server — including "build me an MCP server for X", connecting an AI agent/Claude to a database or API, adding tools/resources to an existing MCP server, reviewing a contributor PR against an MCP server, or…

cyberreinxy/mcp-server-skill · 160 tokens