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 agentmods add instructions/pyang2045/mcp-pushover/claude-mdgit clone --depth 1 https://github.com/pyang2045/mcp-pushoverWrote 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/instructions/pyang2045/mcp-pushover/claude-md)<a href="https://agentmods.dev/instructions/pyang2045/mcp-pushover/claude-md"><img src="https://agentmods.dev/badge/instructions/pyang2045/mcp-pushover/claude-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00428 | $0.00428 |
| Opus 5 | $0.00214 | $0.00214 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
mcp-pushover CLAUDE.md 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 4d 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.
What it actually says
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is an MCP-over-stdio to Pushover bridge implementation in Node.js/TypeScript. The bridge acts as a server that communicates via STDIN/STDOUT using the MCP 2.1 protocol and sends push notifications through the Pushover API.
Development Commands
# Install dependencies
npm install
# Build TypeScript to JavaScript
npm run build
# Run in development mode with ts-node
npm run dev
# Run tests
npm test
# Lint code
npm run lint
# Type check
npm run typecheck
Architecture
The system follows a modular architecture with these core components:
- stream.ts: Handles STDIN/STDOUT communication using
split2for line parsing - mcp-parser.ts: Stateful parser for MCP protocol messages, handles authentication and message assembly
- pushover.ts: HTTP client wrapper for Pushover API using
got - router.ts: Message routing logic, converts MCP messages to internal events
- index.ts: Main entry point, orchestrates handshake and event flow
Protocol Flow
- Server sends initial MCP version handshake
- Client responds with authentication key
- Both exchange capability negotiation messages
- Normal message flow begins, with
#$#dns-com-yourorg-push-sendtriggering push notifications
Key Dependencies
typescript&ts-node: Development and compilationsplit2: Line-based stream parsinggot: HTTP client for Pushover APIdotenv: Environment variable management
Environment Configuration
Required environment variables in .env:
PUSHOVER_TOKEN: Pushover application tokenPUSHOVER_USER: Pushover user key
Testing Strategy
- Unit tests with Jest for parser and API mocking
- Integration tests using scripted MCP flows and HTTP request mocking with
nock
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.
- 4d ago First seen · 64 lines · 428 tokens per session scan A 30ecc2128233
mcp-pushover CLAUDE.md is an instructions file published in the GitHub repository pyang2045/mcp-pushover (2 stars, last pushed 1y ago), licensed MIT. It adds 428 tokens to every session, about $0.0021 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.