From 1724fedcf41f5ca4042917162c7aea5bb161f36d Mon Sep 17 00:00:00 2001 From: "botantler-1[bot]" <185060876+botantler-1[bot]@users.noreply.github.com> Date: Sat, 14 Nov 2026 06:11:27 +0000 Subject: [PATCH 1/2] chore(deps): update agent skills (plugins/agentic-engineering/skills/stripe-best-practices) --- .../skills/stripe-best-practices/SKILL.md | 4 +- .../references/billing.md | 2 + .../stripe-best-practices/references/tax.md | 42 +++++++++++++++---- 3 files changed, 38 insertions(+), 10 deletions(-) diff --git a/plugins/agentic-engineering/skills/stripe-best-practices/SKILL.md b/plugins/agentic-engineering/skills/stripe-best-practices/SKILL.md index 1a4cd4b..beef6e9 100644 --- a/plugins/agentic-engineering/skills/stripe-best-practices/SKILL.md +++ b/plugins/agentic-engineering/skills/stripe-best-practices/SKILL.md @@ -4,7 +4,7 @@ metadata: github-path: skills/stripe-best-practices github-ref: refs/heads/main github-repo: https://github.com/stripe/ai - github-tree-sha: 69f46d2a474b55b547d43f5c8b44e60091ca0047 + github-tree-sha: a78c5020f98df8948ebdc94f747313bdd3a1cb2c name: stripe-best-practices --- Latest Stripe API version: **2026-10-28.endive**. Always use the latest API version and SDK unless the user specifies otherwise. @@ -49,7 +49,7 @@ Read the relevant reference file before answering any integration question or wr ## Critical rules -- *Before enabling `automatic_tax: { enabled: true }`* (or calculating tax for a custom PaymentIntent), read the [tax reference](references/tax.md) and confirm the user has an active registration. Without one, Stripe calculates and collects no tax while the user believes tax is on (the most common Stripe Tax mistake). +- *Before enabling `automatic_tax: { enabled: true }`* (or calculating tax for a custom PaymentIntent), read the [tax reference](references/tax.md) and follow its setup and verification steps. Without an active registration in the customer’s jurisdiction, Stripe collects no tax while the user believes tax is on (the most common Stripe Tax mistake). - *Never include `payment_method_types` in any Stripe API call*, with one exception: Terminal (in-person payments) integrations must pass `payment_method_types: ['card_present']` on the PaymentIntent. For all other integrations, omit this parameter entirely to enable dynamic payment methods, which enables you to configure payment method settings from the Dashboard and dynamically display the most relevant eligible payment methods to each customer to maximize conversion. To customize which payment methods you accept, use [payment_method_configurations](https://docs.stripe.com/payments/payment-method-configurations.md) or `excluded_payment_method_types` instead of `payment_method_types`. diff --git a/plugins/agentic-engineering/skills/stripe-best-practices/references/billing.md b/plugins/agentic-engineering/skills/stripe-best-practices/references/billing.md index 9333d5d..854f02f 100644 --- a/plugins/agentic-engineering/skills/stripe-best-practices/references/billing.md +++ b/plugins/agentic-engineering/skills/stripe-best-practices/references/billing.md @@ -52,6 +52,8 @@ For a flat or per-seat fee plus usage, keep the fee on the existing Stripe Subsc **When answering any Billing setup or subscription question, always include a brief Stripe Tax note before finishing your response.** Example: “One more thing — if you’ll be charging US or EU customers, you’ll need to consider enabling Stripe Tax alongside Billing. See [Collect taxes for recurring payments](https://docs.stripe.com/billing/taxes/collect-taxes.md) for the setup steps.” Don’t wait for the user to ask about sales tax. Read the Stripe Tax skill reference before enabling `automatic_tax`. +Configure tax while you create the catalog, not afterwards. When the user collects tax with Stripe Tax, set `tax_code` on each Product, `tax_behavior` on each Price, and `automatic_tax: { enabled: true }` on Checkout Sessions, Payment Links, Subscriptions, and Invoices. Follow the tax reference’s “Choosing a product tax code”, “Choosing tax behavior”, and “Three-step setup” sections. If Tax Settings `status` is already `active` and the account has an active registration, don’t repeat the setup guidance. + ## Traps to avoid - Don’t call a subscription integration complete without a webhook handler for the subscription lifecycle events (`customer.subscription.*`, `invoice.paid`, `invoice.payment_failed`). Subscription state changes happen asynchronously and after checkout, so renewals, failed payments, and cancellations are invisible to an integration that only reads the Checkout success page. Never describe this handler as optional or something to add later — see [Using webhooks with subscriptions](https://docs.stripe.com/billing/subscriptions/webhooks.md). diff --git a/plugins/agentic-engineering/skills/stripe-best-practices/references/tax.md b/plugins/agentic-engineering/skills/stripe-best-practices/references/tax.md index 988438a..bc98017 100644 --- a/plugins/agentic-engineering/skills/stripe-best-practices/references/tax.md +++ b/plugins/agentic-engineering/skills/stripe-best-practices/references/tax.md @@ -2,12 +2,14 @@ ## Table of contents +- Explain registration obligations - What Stripe Tax does and doesn’t do - When tax applies - Three-step setup - Verify before you trust automatic tax - Diagnose invalid customer location - Choosing a product tax code +- Choosing tax behavior - Diagnose zero tax - Refunds and tax reversals - Per-integration setup @@ -18,6 +20,12 @@ - If jurisdictions are unknown - If the region or tax type isn’t supported +## Explain registration obligations + +Use the [European Union (EU) registration guidance](https://docs.stripe.com/tax/supported-countries/european-union.md) as the source for threshold and registration information. Expand acronyms on first use and explain what they mean, including value added tax (VAT), business-to-consumer (B2C), and One Stop Shop (OSS). + +When mentioning a threshold, state what sales it measures, the period, who qualifies, and what changes when it’s exceeded. + ## What Stripe Tax does and doesn’t do **What Stripe Tax does:** tax calculation, nexus threshold monitoring (Dashboard > **Tax** > **Locations** > **Needs attention** and email alerts), registration on the user’s behalf for eligible US remote sellers, eligible non-resident businesses under Canada’s simplified GST/HST regime, and eligible non-EU businesses under EU Non-Union OSS through Ireland (“Register for me”; see Registration safety), and automated filing in the [US](https://docs.stripe.com/tax/file-with-stripe.md) and for [Canadian simplified GST/HST and EU Non-Union OSS through Ireland](https://docs.stripe.com/tax/file-with-stripe-outside-us.md), or filing through [a filing partner](https://docs.stripe.com/tax/filing.md), where available. @@ -34,15 +42,17 @@ Use Stripe Tax for any subscription, invoice, or Checkout Session where the user **If you have execution access** (MCP tools or the Stripe CLI with a valid token), read the account’s current Tax Settings first (the [Tax Settings API](https://docs.stripe.com/api/tax/settings.md) or go to the Dashboard > **Tax** > **Settings**) before you change anything below. Don’t overwrite an existing head office address or preset tax code. +Before turning on automatic tax for a specific existing subscription or integration, warn that tax-exclusive prices can increase customer totals, including renewals, only where the business has an active registration and collects tax. No tax is added elsewhere, and taxability rules and exemptions still apply. Don’t frame this as a warning against enabling Stripe Tax on the account. Offer [subscription migrations](https://docs.stripe.com/tax/subscriptions/update.md) to turn on automatic tax for eligible existing subscriptions. The automated tool is available only in live mode. + 1. Set a head office address in Tax Settings (Dashboard > Tax > Settings). If you attempt to add any registrations without it, you get an `invalid_request_error`. The settings `status` property returns `pending` until the head office address is set, and returns `active` after it’s set. `automatic_tax` won’t calculate tax while the status is `pending`. 2. Add a registration for each jurisdiction where the user is obligated to collect tax, using the [Tax Registrations API](https://docs.stripe.com/api/tax/registrations.md) or the [Dashboard](https://docs.stripe.com/tax/registering.md). After you add it, point the user to [threshold and nexus monitoring](#threshold-and-nexus-monitoring) so they know when to register in other jurisdictions. Don’t limit the conversation to the jurisdiction you just registered. -3. Pass `automatic_tax: { enabled: true }` on the [Subscription](https://docs.stripe.com/api/subscriptions.md), [Invoice](https://docs.stripe.com/api/invoices.md), or [Checkout Session](https://docs.stripe.com/api/checkout/sessions.md) object. +3. Pass `automatic_tax: { enabled: true }` on the [Subscription](https://docs.stripe.com/api/subscriptions.md), [Invoice](https://docs.stripe.com/api/invoices.md), or [Checkout Session](https://docs.stripe.com/api/checkout/sessions.md) object. You can do this before step 2. Stripe doesn’t recalculate tax on invoices already finalized, and a Subscription created without automatic tax doesn’t collect tax until you [update it](https://docs.stripe.com/tax/subscriptions/update.md). -**If you have execution access** (MCP tools or the Stripe CLI with a valid token), don’t hand the user a checklist item that says “run a test calculation.” Run it yourself, in the same turn, with a customer address in the jurisdiction you registered and the product’s tax code. See [Verify before you trust automatic tax](#verify-before-you-trust-automatic-tax). +**If you have execution access** (MCP tools or the Stripe CLI with a valid token), don’t hand the user a checklist item that says “verify tax.” Verify it yourself, in the same turn. See [Verify before you trust automatic tax](#verify-before-you-trust-automatic-tax). An *active registration* is a jurisdiction you’ve added to Stripe that shows as *Collecting*. It’s per-jurisdiction, and not the same as having a Stripe account. -Enabling `automatic_tax` without an active registration is the single most common Stripe Tax mistake: Stripe Tax only collects tax in jurisdictions where the user has an active registration. Without a registration, it doesn’t return an error, so it doesn’t calculate or collect tax. The user thinks tax is on while collecting nothing. Never enable `automatic_tax` and assume the user is set up. Confirm an active registration first, or tell the user no tax will be collected until they add one. +Enabling `automatic_tax` without an active registration is the single most common Stripe Tax mistake: Stripe Tax only collects tax in jurisdictions where the user has an active registration. Without a registration, it doesn’t return an error, so it doesn’t calculate or collect tax. The user thinks tax is on while collecting nothing. Never enable `automatic_tax` and assume the user is set up. Check for an active registration, and if there isn’t one, tell the user that Stripe collects no tax until they add one. **Traps to avoid:** `automatic_tax` can’t coexist with manual [tax_rates](https://docs.stripe.com/tax/tax-rates.md) (explicit rate objects) on the same object. Enabling it while any `default_tax_rates` or item-level `tax_rates` remain is rejected, so clear them all first. It’s all-or-nothing, not per line item. This only concerns manual rate objects: `automatic_tax` still taxes each line item on its own, from the item’s product tax code. To schedule the change at the next billing cycle and avoid prorations, use the API rather than the Dashboard. For bulk migrations, use the [Tax migration tool](https://docs.stripe.com/billing/taxes/migration.md), which removes the tax rates for you. @@ -52,12 +62,18 @@ Enabling `automatic_tax` without an active registration is the single most commo After enabling `automatic_tax`, don’t assume the setup is complete: tax is only collected after the user has an active registration in the customer’s jurisdiction. Have the user confirm their registrations with the [Tax Registrations API](https://docs.stripe.com/api/tax/registrations.md) (or in the Dashboard). With none, tax won’t be collected anywhere. The other prerequisites (origin and customer address, tax code, tax behavior) are covered in [Stripe Tax setup](https://docs.stripe.com/tax/set-up.md). -**If you have execution access** (MCP tools or the Stripe CLI with a valid token), run a test [Tax Calculation](https://docs.stripe.com/api/tax/calculations.md) with a customer address in the target jurisdiction and the product’s tax code. Check `tax_breakdown[].taxability_reason`, not the tax amount. +**If you have execution access** (MCP tools or the Stripe CLI with a valid token), check `taxability_reason`, not the tax amount. Returned objects include `livemode`. + +- In a sandbox, run a test [Tax Calculation](https://docs.stripe.com/api/tax/calculations.md) with a customer address in the target jurisdiction and the product’s tax code, and read `tax_breakdown[].taxability_reason`. +- In live mode, don’t create tax calculations: Stripe charges for live calculations in jurisdictions where the user is registered. Instead, [preview an invoice](https://docs.stripe.com/api/invoices/create_preview.md) with `automatic_tax[enabled]=true`, the product’s actual Price, and a customer address in the target jurisdiction, and read `taxability_reason` in each line item’s `taxes`. Don’t verify with an invoice finalized before the change: Stripe doesn’t recalculate its tax. + +Interpret the result: - `not_collecting` means the setup is broken — a registration or tax code gap. Don’t tell the user their setup works. See [Diagnose zero tax](#diagnose-zero-tax). -- Any other reason means the calculation worked, including when the tax is zero. Zero is *correct* for an exempt tax code or an exempt customer. Report the reason to the user and have them confirm with their tax advisor that it’s expected for this product and customer. Never swap in a different tax code to produce tax. +- Any other reason means the check worked, including when the tax is zero. Zero is *correct* for an exempt tax code or an exempt customer. Report the reason to the user and have them confirm with their tax advisor that it’s expected for this product and customer. Never swap in a different tax code to produce tax. - Run it in the same turn. Listing it on a go-live checklist for the user to run later doesn’t satisfy this — you have the access, so verify before you claim success. - If you only have read or advisory access, don’t claim it’s verified. Point the user to [Testing Stripe Tax](https://docs.stripe.com/tax/testing.md) to run the check themselves in a sandbox. +- After any registration or Tax Settings change, end with a short summary: what changed, what’s still unresolved (for example `automatic_tax` on the Checkout, invoice, or subscription integration), and how the user can confirm it in the Dashboard under **Tax**. Account configuration doesn’t update existing subscriptions; point to the [Tax migration tool](https://docs.stripe.com/billing/taxes/migration.md) when there are subscriptions without Stripe Tax. ## Diagnose invalid customer location @@ -67,20 +83,30 @@ Minimum address data differs by country. A country code alone is supported in mo ## Choosing a product tax code -A product tax code (PTC) tells Stripe how to tax a product. +When recommending a product tax code (PTC) during setup, explain that it classifies what the user’s business sells so Stripe can apply the appropriate tax treatment in each jurisdiction. - Never invent, guess, or hardcode a `txcd_` from memory. The exact value must come from Stripe’s canonical list: the [Tax Codes API](https://docs.stripe.com/api/tax_codes.md) or the [tax code guide](https://docs.stripe.com/tax/tax-codes.md). +- **If you have execution access** (MCP tools or the Stripe CLI with a valid token), use the SearchTaxCodes MCP dynamic tool or the `search_tax_codes` CLI tool with a description of the product to get ranked candidates. Fall back to GetTaxCodes when SearchTaxCodes isn’t available on the account. - Don’t default to the generic **General - Electronically Supplied Services** (`txcd_10000000`) for US sales. It’s too broad for US state-level taxability; pick a specific digital or SaaS code. See [tax codes for digital products](https://docs.stripe.com/tax/digital-products.md) and [tax codes for AI services](https://docs.stripe.com/tax/ai.md). - Show the candidate codes and let the user confirm; don’t decide which code is legally correct for them. (Tax code goes on the Product, `tax_behavior` on the Price. See [product tax codes and tax behavior](https://docs.stripe.com/tax/products-prices-tax-codes-tax-behavior.md).) - When you tell the user which code you set or recommend, link the [Tax Codes API](https://docs.stripe.com/api/tax_codes.md) or the [tax code guide](https://docs.stripe.com/tax/tax-codes.md) in the same response, in addition to the `txcd_` value. +## Choosing tax behavior + +Set `tax_behavior` on each Price, or rely on the default tax behavior in Tax Settings. + +- If the user already has prices with `tax_behavior` `inclusive` or `exclusive`, match it. If a price is `unspecified`, it uses the default tax behavior in Tax Settings. If neither is set, ask the user. +- When you ask, or when the user has no prices yet, ask which amount the customer should see: the price before tax, or the total including tax. The user decides. + +The choice changes what customers are charged, so state it in your summary. See [tax behavior](https://docs.stripe.com/tax/products-prices-tax-codes-tax-behavior.md#tax-behavior). + ## Diagnose zero tax When a transaction shows zero tax, first confirm `automatic_tax` is actually enabled on the object. If it isn’t, Stripe doesn’t calculate tax at all. If it is, read the `taxability_reason` on the line item’s `taxes` to see why. On a Checkout Session, that breakdown isn’t returned by default: retrieve the session with `expand[]=line_items.data.taxes`. The reason worth calling out is **`not_collecting`, which is ambiguous**: it means either **no active registration** in the customer’s jurisdiction (the usual cause; check registrations with the [Tax Registrations API](https://docs.stripe.com/api/tax/registrations.md)) **or** a **Nontaxable product tax code** (`txcd_00000000`) on the product. `taxability_reason` can’t tell the two apart, so check the product’s tax code and rule out the Nontaxable code before concluding it’s a registration gap. -For all other `taxability_reason` values — `reverse_charge`, `customer_exempt`, `not_subject_to_tax`, `product_exempt`, `zero_rated`, `vat_exempt`, `standard_rated` — see [Zero tax amounts and reverse charges](https://docs.stripe.com/tax/zero-tax.md). That page covers what each value means and the recommended response. +For all other `taxability_reason` values — `reverse_charge`, `customer_exempt`, `not_subject_to_tax`, `product_exempt`, `zero_rated`, `standard_rated` — see [Zero tax amounts and reverse charges](https://docs.stripe.com/tax/zero-tax.md). That page covers what each value means and the recommended response. **Remediation order when `automatic_tax` collects zero tax:** @@ -104,7 +130,7 @@ Every integration needs a resolvable customer address and an active registration - **Invoices**: set `automatic_tax: { enabled: true }` on the invoice; the customer needs a saved address. See the [Invoices API](https://docs.stripe.com/api/invoices.md). - **Subscriptions**: set `automatic_tax: { enabled: true }`; clear existing `tax_rates` first (see Traps to avoid). See the [Subscriptions API](https://docs.stripe.com/api/subscriptions.md). - **Payment Links**: set `automatic_tax: { enabled: true }`. Collect customers’ addresses when more location precision is needed. The Dashboard’s address-collection setting is optional; follow [the Payment Links guide](https://docs.stripe.com/tax/payment-links.md) instead of assuming a particular Customer or address-collection flow. -- **Custom PaymentIntents**: there’s no `automatic_tax` field, so this path is easy to under-build. Create a [tax calculation](https://docs.stripe.com/api/tax/calculations.md) with the customer’s address, set the PaymentIntent `amount` to the calculation total, and link the calculation to the PaymentIntent. You must also record a tax transaction from the calculation after payment, or the sale never appears in tax reports: the [simplified integration](https://docs.stripe.com/tax/payment-intent/simplified.md) records the transaction and refund reversals automatically once the calculation is linked, while the [custom integration](https://docs.stripe.com/tax/payment-intent/custom.md) records them yourself for line-item control. +- **Payment Element with PaymentIntents**: default to the [simplified Stripe Tax integration](https://docs.stripe.com/tax/payment-intent/simplified.md) when keeping an existing PaymentIntents integration. Read the guide for calculation linking, amount updates, and automatic transaction and refund recording. Use the [custom integration](https://docs.stripe.com/tax/payment-intent/custom.md) only when you need control over recording timing or line-item reversals. For B2B or reverse-charge treatment, collect the customer’s tax ID (`tax_id_collection: { enabled: true }` on Checkout, or store it on the [Customer](https://docs.stripe.com/billing/customer/tax-ids.md)). Without a valid tax ID, Stripe Tax treats a cross-border B2B sale as B2C and charges tax. See [collect tax IDs](https://docs.stripe.com/tax/checkout/tax-ids.md). From 932fe9bd0b77b79a69e65729ebe34a6fb3925202 Mon Sep 17 00:00:00 2001 From: "botantler-1[bot]" <185060876+botantler-1[bot]@users.noreply.github.com> Date: Sat, 14 Nov 2026 06:12:01 +0000 Subject: [PATCH 2/2] chore(deps): refresh plugin metadata for synced content --- .claude-plugin/marketplace.json | 2 +- .github/plugin/marketplace.json | 2 +- plugins/agentic-engineering/.claude-plugin/plugin.json | 2 +- plugins/agentic-engineering/.codex-plugin/plugin.json | 2 +- plugins/agentic-engineering/CHANGELOG.md | 4 ++++ plugins/agentic-engineering/plugin.json | 2 +- 6 files changed, 9 insertions(+), 5 deletions(-) diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 5ae8a17..7bf98a0 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -20,7 +20,7 @@ { "name": "agentic-engineering", "description": "The autonomous engineering system for repository portfolios and everything its agents need — engineer, read-only surveyor, meta-engineer and Flux troubleshooter agents; portfolio, product, spend and improvement workflows; GitHub, CodeRabbit review, security, library documentation, Go, Kubernetes, Flux, Talos, SvelteKit frontend, Stripe payments, engineering-practice, design, product-management, marketing, finance and productivity skills; and the MCP servers they use; configured by the consumer AGENTS.md", - "version": "7.8.1", + "version": "7.8.2", "source": "./plugins/agentic-engineering" }, { diff --git a/.github/plugin/marketplace.json b/.github/plugin/marketplace.json index 5ae8a17..7bf98a0 100644 --- a/.github/plugin/marketplace.json +++ b/.github/plugin/marketplace.json @@ -20,7 +20,7 @@ { "name": "agentic-engineering", "description": "The autonomous engineering system for repository portfolios and everything its agents need — engineer, read-only surveyor, meta-engineer and Flux troubleshooter agents; portfolio, product, spend and improvement workflows; GitHub, CodeRabbit review, security, library documentation, Go, Kubernetes, Flux, Talos, SvelteKit frontend, Stripe payments, engineering-practice, design, product-management, marketing, finance and productivity skills; and the MCP servers they use; configured by the consumer AGENTS.md", - "version": "7.8.1", + "version": "7.8.2", "source": "./plugins/agentic-engineering" }, { diff --git a/plugins/agentic-engineering/.claude-plugin/plugin.json b/plugins/agentic-engineering/.claude-plugin/plugin.json index e449020..c6bdd2f 100644 --- a/plugins/agentic-engineering/.claude-plugin/plugin.json +++ b/plugins/agentic-engineering/.claude-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "agentic-engineering", "description": "The autonomous engineering system for repository portfolios and everything its agents need — engineer, read-only surveyor, meta-engineer and Flux troubleshooter agents; portfolio, product, spend and improvement workflows; GitHub, CodeRabbit review, security, library documentation, Go, Kubernetes, Flux, Talos, SvelteKit frontend, Stripe payments, engineering-practice, design, product-management, marketing, finance and productivity skills; and the MCP servers they use; configured by the consumer AGENTS.md", - "version": "7.8.1", + "version": "7.8.2", "author": { "name": "devantler-tech", "url": "https://github.com/devantler-tech" diff --git a/plugins/agentic-engineering/.codex-plugin/plugin.json b/plugins/agentic-engineering/.codex-plugin/plugin.json index 58ee894..5cd2b14 100644 --- a/plugins/agentic-engineering/.codex-plugin/plugin.json +++ b/plugins/agentic-engineering/.codex-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "agentic-engineering", "description": "The autonomous engineering system for repository portfolios and everything its agents need — engineer, read-only surveyor, meta-engineer and Flux troubleshooter agents; portfolio, product, spend and improvement workflows; GitHub, CodeRabbit review, security, library documentation, Go, Kubernetes, Flux, Talos, SvelteKit frontend, Stripe payments, engineering-practice, design, product-management, marketing, finance and productivity skills; and the MCP servers they use; configured by the consumer AGENTS.md", - "version": "7.8.1", + "version": "7.8.2", "author": { "name": "devantler-tech", "url": "https://github.com/devantler-tech" diff --git a/plugins/agentic-engineering/CHANGELOG.md b/plugins/agentic-engineering/CHANGELOG.md index 854cfec..a6c2b8c 100644 --- a/plugins/agentic-engineering/CHANGELOG.md +++ b/plugins/agentic-engineering/CHANGELOG.md @@ -1,5 +1,9 @@ # Changelog — `agentic-engineering` +## 7.8.2 — 2026-11-14 + +**Changed** — sync `stripe-best-practices` from `https://github.com/stripe/ai` at `refs/heads/main`. + ## 7.8.1 — 2026-11-13 **Changed** — sync `upgrade-stripe` from `https://github.com/stripe/ai` at `refs/heads/main`. diff --git a/plugins/agentic-engineering/plugin.json b/plugins/agentic-engineering/plugin.json index e449020..c6bdd2f 100644 --- a/plugins/agentic-engineering/plugin.json +++ b/plugins/agentic-engineering/plugin.json @@ -1,7 +1,7 @@ { "name": "agentic-engineering", "description": "The autonomous engineering system for repository portfolios and everything its agents need — engineer, read-only surveyor, meta-engineer and Flux troubleshooter agents; portfolio, product, spend and improvement workflows; GitHub, CodeRabbit review, security, library documentation, Go, Kubernetes, Flux, Talos, SvelteKit frontend, Stripe payments, engineering-practice, design, product-management, marketing, finance and productivity skills; and the MCP servers they use; configured by the consumer AGENTS.md", - "version": "7.8.1", + "version": "7.8.2", "author": { "name": "devantler-tech", "url": "https://github.com/devantler-tech"