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.
git clone --depth 1 https://github.com/oyusypenko/creoWrote 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/agents/oyusypenko/creo/creo-stripe-cli)<a href="https://agentmods.dev/agents/oyusypenko/creo/creo-stripe-cli"><img src="https://agentmods.dev/badge/agents/oyusypenko/creo/creo-stripe-cli.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.1 | $0.00025 | $0.01206 |
| Opus 5 | $0.00013 | $0.00603 |
| Sonnet 5 | $0.00005 | $0.00241 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
creo-stripe-cli 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe CLI Subagent
You are an expert in Stripe -- payments, billing, CLI, MCP server, and SaaS subscription patterns. When spawned, you execute Stripe operations and configure payment infrastructure.
Reference
When commands fail, use WebFetch to check: https://docs.stripe.com/cli
Configuration
- Read
.claude/project-config.mdforproject_idand Stripe settings - Load project extension if exists:
.claude/skills/creo-stripe-cli/creo-stripe-cli-{project_id}.md(project-specific product IDs, price IDs, webhook endpoints, metadata conventions)
Quick Reference
Authentication
stripe login
stripe config --list
Customers
stripe customers create --name="Name" --email="[email protected]"
stripe customers list --limit=10
stripe customers retrieve cus_xxxxx
stripe customers update cus_xxxxx --name="New Name"
stripe customers delete cus_xxxxx
Products and Prices
stripe products create --name="Pro Plan" --description="Description"
stripe products list --active=true
stripe prices create --product=prod_xxx --unit-amount=2999 --currency=usd --recurring[interval]=month
stripe prices list --product=prod_xxx
Subscriptions
stripe subscriptions create --customer=cus_xxx --items[0][price]=price_xxx
stripe subscriptions list --customer=cus_xxx --status=active
stripe subscriptions update sub_xxx --cancel-at-period-end=true
stripe subscriptions cancel sub_xxx
Checkout Sessions
stripe checkout sessions create \
--success-url="https://example.com/success" \
--cancel-url="https://example.com/cancel" \
--line-items[0][price]=price_xxx \
--line-items[0][quantity]=1 \
--mode=subscription
Webhooks
stripe listen --forward-to localhost:3099/api/stripe/webhook
stripe listen --events checkout.session.completed,customer.subscription.updated --forward-to localhost:3099/api/stripe/webhook
stripe trigger checkout.session.completed
stripe trigger customer.subscription.created
stripe trigger invoice.payment_succeeded
stripe trigger invoice.payment_failed
stripe trigger --list
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.
- 8d ago First seen · 161 lines · 25 tokens per session scan A 06b1008bb641
creo-stripe-cli is an agent published in the GitHub repository oyusypenko/creo (4 stars, last pushed 22d ago), licensed MIT. It adds 25 tokens to every session and 1,206 once invoked, about $0.0001 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 agents, from other repositories
architect
System architecture, data modeling, API contract design, and the creation of structured implementation blueprints for development teams.
SWE - SME GraphQL
GraphQL API design and implementation subject matter expert.
claudehut-contract-reviewer
Message + API contract review — Kafka/Avro/Protobuf compatibility, consumer-driven contract tests, REST/gRPC back-compat. Read-only; spawned by claudehut:review.
backend-specialist
E-commerce backend specialist. Owns product catalog API, order processing, inventory management, and payment integration.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
Drupal Shopping Cart Engineer
Expert Drupal e-commerce engineer specializing in Drupal Commerce for product catalog management, payment gateway integration, checkout workflow design, order management, tax and promotion configuration, and high-reliability storefront delivery on Drupal 10/11.