cli CLAUDE.md

Project instructions for building and running the SuprSend command-line application, a Go tool for working with a notification service.

In plain words
What is it for?
Running the tool, building binaries, generating release artifacts, cleaning files, and understanding its main Go code areas.
Why use it?
They collect the repository’s local commands and technical conventions in one place, including the absence of tests.

Instructions file

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.

agentmods
npx agentmods add instructions/suprsend/cli/claude-md
Clone the repo
git clone --depth 1 https://github.com/suprsend/cli
Per session 1,796 This file is loaded in full into every session.
When invoked 1,796 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01796 $0.01796
Opus 5 $0.00898 $0.00898
Sonnet 5 $0.00359 $0.00359
Haiku 4.5 $0.00180 $0.00180

Measured 2d ago against content hash e3efa0207605, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cli 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 2d 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.

CLAUDE.md · 90 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Build & Run Commands

# Build and run locally
go run ./cmd/suprsend/main.go

# Build binary
cd cmd/suprsend && go build -o suprsend

# Full build: compile type-morph binary (requires deno), generate docs and skills
make build

# Clean build artifacts
make clean

# Full release build with goreleaser (generates docs, builds all platforms)
./scripts/build.sh              # snapshot build
./scripts/build.sh release      # release build

There are no tests in this project.

Architecture

This is a Go CLI tool built with cobra for interacting with the SuprSend notification infrastructure API. It also serves as an MCP server for AI tool integrations.

Key Layers

  • cmd/suprsend/main.go — Entrypoint, calls commands.Execute()
  • internal/commands/root.go — Root cobra command. Registers all subcommands and handles service token resolution (env > flag > config file profile)
  • internal/commands/ — Each resource type (workflow, event, schema, category, translation, profiles) is a subpackage with its own cobra subcommands (list, pull, push, commit)
  • mgmnt/ — API client layer (SS_MgmntClient). Makes HTTP calls to SuprSend management API. Each resource type has its own file (workflow.go, event.go, schema.go, etc.)
  • internal/tools/ — MCP tool definitions. Each file registers tools via RegisterTool() into a global registry. The MCP server (startMcpServer.go) selects and serves these tools
  • internal/config/ — Global config singleton (config.Cfg) using viper. Config file is $HOME/.suprsend.yaml
  • internal/utils/ — SDK singleton (SDKInstance), output formatting, embedded binaries

Command Pattern

Each resource follows a consistent pattern:

  • helpers.go — Shared file I/O functions (read/write JSON files)
  • <resource>.go — Parent cobra command
  • <resource>_get.go, <resource>_list.go, <resource>_pull.go, <resource>_push.go, <resource>_commit.go — CRUD subcommands

Read the full file on GitHub · 90 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. 2d ago First seen · 90 lines · 1,796 tokens per session scan A e3efa0207605

Subscribe to this mod's changes

cli CLAUDE.md is an instructions file published in the GitHub repository suprsend/cli (12 stars, last pushed 1mo ago), licensed MIT. It adds 1,796 tokens to every session, about $0.0090 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-30.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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.

langchain-ai/langchain · 4,345 tokens