stripekit AGENTS.md

A set of instructions for AI agents working on StripeKit, a command-line tool that turns a written Stripe configuration into billing code and matching settings in a Stripe account.

In plain words
What is it for?
It helps agents understand, test, build, and release StripeKit, including its configuration loader, change-planning process, command-line commands, and generated billing templates.
Why use it?
It gives an agent the project layout, setup commands, testing guidance, and release details needed to make safe changes in the codebase.

Instructions file for CodexOpenCode

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/rafaelcg/stripekit/agents-md
Clone the repo
git clone --depth 1 https://github.com/rafaelcg/stripekit

Made for: Codex, OpenCode.

Per session 1,047 This file is loaded in full into every session.
When invoked 1,047 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.01047 $0.01047
Opus 5 $0.00524 $0.00524
Sonnet 5 $0.00209 $0.00209
Haiku 4.5 $0.00105 $0.00105

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

Security

Grade A, and why

stripekit AGENTS.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.

AGENTS.md · 70 lines

How it starts

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

AGENTS.md

Guidance for AI agents working on the stripekit codebase. (To learn how to use stripekit in a project, read SKILL.md or llms.txt instead.)

What this is

stripekit is the "create-next-app of Stripe": a CLI that reconciles a declarative stripe.config.ts into the user's own Stripe account and scaffolds correct billing code. It is a tool, not a platform — no hosted service, no runtime dependency in generated code. See README.md and DESIGN.md for the full picture.

Layout

  • packages/stripekit/src/ — the CLI + library.
    • config/defineConfig, zod schema, TS config loader.
    • reconciler/ — the core: desired.ts (config → desired state), diff.ts (pure diff → plan), apply.ts, read-state.ts, pull.ts, plan.ts.
    • cli/commands/init, plan, push, pull, dev, check.
    • init/ — framework/auth detection + scaffolding.
  • packages/stripekit/templates/init/ — the billing code emitted by init (real TS files, not compiled by the tool).
  • packages/stripekit/test/ — vitest; fake-stripe.ts is an in-memory Stripe used to test the whole reconcile loop offline.
  • docs/ — VitePress site. examples/playground/ — a scratch project.

Setup & commands

Node 20+ and pnpm. From the repo root:

pnpm install
pnpm -C packages/stripekit build       # bundle CLI + types (tsup)
pnpm -C packages/stripekit test        # vitest
pnpm -C packages/stripekit typecheck   # tsc --noEmit
pnpm format                            # prettier
pnpm docs:build                        # build the docs site

Always run test, typecheck, and format before committing.

Releasing

stripekit is published to npm. Keep one version number across packages/stripekit/package.json, src/constants.ts (VERSION), docs/public/.well-known/mcp/server-card.json, server.json, .claude-plugin/plugin.json, and .claude-plugin/marketplace.json.

Read the full file on GitHub · 70 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 · 70 lines · 1,047 tokens per session scan A e3e98f8e7896

Subscribe to this mod's changes

stripekit AGENTS.md is an instructions file published in the GitHub repository rafaelcg/stripekit (2 stars, last pushed 25d ago), licensed MIT. It adds 1,047 tokens to every session, about $0.0052 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.

Related

Other instructions, from other repositories