Security audit
Security checks for vulnerabilities and agentic risk
This skill can spend ARI credits without prior cost approval, exceed a spending threshold, and revive unanswered quotes for paid execution later.
Set ARI to ask before every charge and use the dedicated quote command for estimates; omitting --confirm does not reliably prevent spending. Approve recurring monitoring separately. Prefer a corrected version that enforces combined spending limits and never treats an unanswered quote as permission.
scripts/ari.pyAnalysis-only automatic approval authorizes additional collection charges
Credits can be consumed beyond the user's configured no-confirmation spending limit without requesting approval. For example, analysis and collection can each fall below the limit while their combined cost exceeds it.
The broader analytics and monitoring features are not inherently vulnerabilities, particularly where explicit confirmation is required. However, the skill also directs credit-consuming execution based on provider-defined first-run policies rather than demonstrated user spending authorization, exposing users of an ostensibly review-alert skill to unexpected charges.
The snippet exposes competitor tracking and comparative trend analysis, neither of which is declared in the review-alert description. These are distinct user-facing capabilities rather than merely supporting implementation details. The snippet does not show alert retrieval, negative-review detection, or review analysis. Because the implementation of ari.py is not supplied, this assessment is limited to the behavior indicated by the commands and their comments.
Although related to negative reviews, the supplied command performs a distinct, undeclared leaderboard operation. It does not show subscription monitoring, alert retrieval, or review analysis. The implementation of ari.py is not supplied, so additional effects of the command or --confirm cannot be established.
The supplied command explicitly selects analyze --type compare and supplies a competitor ASIN. This is a comparative-analysis operation, not an alert-monitoring, unread-alert retrieval, or identified-negative-review analysis operation. Although it concerns Amazon products, competitor comparison is a distinct undeclared capability. The underlying script is not supplied, so this assessment is limited to the operation requested by the command.
The supplied command explicitly selects analyze --type compare and provides a separate --competitor ASIN. This introduces competitor comparison rather than the declared monitoring, alert retrieval, or negative-review analysis workflow. The script implementation is not supplied, so its underlying data access and side effects cannot be determined.
The supplied command explicitly selects 'operations quote --workflow audit --focus full', rather than review subscriptions, monitoring, alert retrieval, or review analysis. Although it targets an Amazon ASIN, its visible operation is an audit quotation, a materially different capability. The script implementation is not supplied, so no additional behavior or side effects can be established.
The supplied command invokes benchmarking rather than subscribing to monitoring, retrieving alerts, or analyzing problem reviews. This indicates a capability outside the declared purpose. However, the implementation of scripts/ari.py is not supplied, so the benchmark's precise behavior and any relationship to review monitoring cannot be verified.
The skill directs the agent to revive an unanswered quote in a later conversation and proceed to report generation, potentially charging credits if automatic confirmation applies. Silence and an idle product record do not establish current authorization, so an unrelated later interaction can trigger unwanted paid work.
run_analysis converts an absent --confirm into authorization whenever the quote contains sufficient funds and a truthy autoConfirm value. Consequently, analyze and deepdive can consume credits without the explicit confirmation promised by the module; cmd_voc has an analogous bypass that can also initiate paid collection. An official HTTPS response establishes its source, not the user's consent to spending.
In context, the server's autoConfirm flag permits credit-consuming operations without presenting the price for user approval. The documented default policy allows initial paid operations without an amount ceiling, making server policy a substitute for explicit spending authorization; a positive balance does not establish consent.
- 重新发布：各市场首批上架的 1.5.0 包早于免确认修复，新注册的免费版用户仍会被要求先确认报价。
1.5.1 与当前官网下发的修复版一致，市场侧以新版本号覆盖旧包。
- 免确认只认服务端报价返回的 `autoConfirm`；采集报价扣除首次采集免费页；
非美国站首次采集可用赠送积点时不再提示「赠送积点不可用」（行为与修复后的 1.5.0 相同）。
- 命令、字段与计费规则不变，不提高最低支持版本。
The documented policy explicitly allows the first N paid generations without an amount ceiling, automatically collecting data and charging credits. Gift credits, insufficient-balance checks, and optional user thresholds reduce exposure but do not establish a default spending limit or informed authorization.
- 行为变更：新用户（注册并验证邮箱后）第一次要 VOC，只给 ASIN 即可（站点默认美国站），
`voc` 直接执行——自动补采集（默认 3 页）、生成报告、按服务端定价扣费并归档，
不再停在报价等确认。费用在报告返回的 `charges` 字段透明展示（采集/分析/合计/余额前后）。
- 免确认与否**只认服务端报价返回的 `autoConfirm` 布尔**：服务端策略前 N 次付费生成不看金额上限
（新用户赠送积点按设计覆盖「3 页采集 + 一份 VOC」）；用户自设阈值优先、显式要求「每次先问」
时仍先报价；余额不足不自动。客户端不再从 `autoConfirmNote` 文案或 `autoConfirmRemaining`
自行推断——文案匹配会把 Free 小额提示里的「先确认」误判成用户要求每次询问，恰好挡住新用户。
This is another match within the same automatic-spending policy, not a separate vulnerability. Using a typed boolean rather than interpreting explanatory text is appropriate, but that boolean alone does not demonstrate user authorization for an uncapped paid operation.
不再停在报价等确认。费用在报告返回的 `charges` 字段透明展示（采集/分析/合计/余额前后）。
- 免确认与否**只认服务端报价返回的 `autoConfirm` 布尔**：服务端策略前 N 次付费生成不看金额上限
（新用户赠送积点按设计覆盖「3 页采集 + 一份 VOC」）；用户自设阈值优先、显式要求「每次先问」
时仍先报价；余额不足不自动。客户端不再从 `autoConfirmNote` 文案或 `autoConfirmRemaining`
自行推断——文案匹配会把 Free 小额提示里的「先确认」误判成用户要求每次询问，恰好挡住新用户。
- 采集报价同口径扣除服务端 `trialFreePages`（首次采集试用免费页），避免新用户被误报「积点不足」。
- 非美国站：服务端 `credits.gift` 策略下用户首次采集不限站点，`credits/balance` 返回 `giftAllSites`，
This duplicates the automatic-spending issue reported at the same location. Avoiding inference from autoConfirmNote or autoConfirmRemaining is not itself unsafe; the concern is that the surrounding policy permits paid execution based solely on a server flag without a default monetary ceiling.
不再停在报价等确认。费用在报告返回的 `charges` 字段透明展示（采集/分析/合计/余额前后）。
- 免确认与否**只认服务端报价返回的 `autoConfirm` 布尔**：服务端策略前 N 次付费生成不看金额上限
（新用户赠送积点按设计覆盖「3 页采集 + 一份 VOC」）；用户自设阈值优先、显式要求「每次先问」
时仍先报价；余额不足不自动。客户端不再从 `autoConfirmNote` 文案或 `autoConfirmRemaining`
自行推断——文案匹配会把 Free 小额提示里的「先确认」误判成用户要求每次询问，恰好挡住新用户。
- 采集报价同口径扣除服务端 `trialFreePages`（首次采集试用免费页），避免新用户被误报「积点不足」。
- 非美国站：服务端 `credits.gift` 策略下用户首次采集不限站点，`credits/balance` 返回 `giftAllSites`，
The changelog extends automatic paid execution to multiple analysis types whenever autoConfirm is true. Returning charges afterward provides transparency but cannot prevent unintended credit consumption, and the broader operation coverage increases exposure to the same authorization weakness.
为 true 时赠送积点计入 `nonUsCollectCredits`、`siteNote` 为空；UK/DE/JP 卖家的第一份 VOC 同样一步直出。
- 余额不足仍在执行前拦截（402）并引导充值；定价以服务端配置为准，代码常量仅为兜底。
- 一致性：`analyze` 各类型（insight / keywords / trend / variant / compare）走同一口径，
`autoConfirm=true` 即直接生成并返回 `charges`。
- 文档：移除所有写死的单价与合计示例。采集/分析单价与页数由后台 `pricing` 配置决定，
一律以本次报价返回的 `credits` / `totalCredits` 为准，不得凭文档或记忆报数。
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- 能力层收窄：44 个专属包不再只是「声明窄」，包体 `scripts/ari.py` 同时按各自契约裁剪。
构建期用 AST 删除文档未承诺的命令、它们的解析器注册块，以及只被它们引用的辅助函数与
常量；专属包因此不再包含 `export`（任意路径写文件）、`autoconfirm`（撤销逐次确认）、
`workbench`（改写差评处理状态）、`alerts`（标记预警已读）、`competitors`、`schedule`、
`voc` / `analyze` / `charts` / `deepdive` 等母版命令。
- 新增运行期兜底闸：专属包在包内写入 `allowedCommands` 白名单，`ari.py`
Without declared permissions the skill's intent is opaque and cannot be validated.
The autoConfirm policy combines genuine user-set thresholds with provider-defined first-run exemptions that explicitly ignore the amount. Treating both as authorization permits credit deductions without showing that the user agreed to the cost or spending limit.
`voc <ASIN>`（没说站点就用默认的美国站，不要为此追问）。
命中服务端免确认规则（新用户首次体验不看金额 / 账户剩余免确认次数 / 用户自设阈值）且余额充足时，
**直接完成采集 + 生成 + 扣点并归档**，不再停在报价环节。绝不能描述成“先帮你问个价 / 只报价不扣点”。
免确认与否以返回里的 `autoConfirm` 为准，不要自己从提示文案里猜。
- 直接生成成功后，返回结果带 `charges`（采集扣点、分析扣点、合计、扣前/扣后余额）与 `autoConfirmNote`。
**先讲报告，再用一句话转述实际扣点**，不要在拿到结果后再补问「要不要生成」，也不要回头补一次报价。
- 只有在返回 `confirmationRequired: true` 时（余额不足、或用户自行设置了“每次先问”）
This is another occurrence of the same authorization weakness: a server-returned autoConfirm flag is treated as sufficient permission to spend. The documented first-run rules show that the flag can reflect provider policy rather than explicit user consent, and after-the-fact charge disclosure cannot supply that consent.
命中服务端免确认规则（新用户首次体验不看金额 / 账户剩余免确认次数 / 用户自设阈值）且余额充足时，
**直接完成采集 + 生成 + 扣点并归档**，不再停在报价环节。绝不能描述成“先帮你问个价 / 只报价不扣点”。
免确认与否以返回里的 `autoConfirm` 为准，不要自己从提示文案里猜。
- 直接生成成功后，返回结果带 `charges`（采集扣点、分析扣点、合计、扣前/扣后余额）与 `autoConfirmNote`。
**先讲报告，再用一句话转述实际扣点**，不要在拿到结果后再补问「要不要生成」，也不要回头补一次报价。
- 只有在返回 `confirmationRequired: true` 时（余额不足、或用户自行设置了“每次先问”）
才报出 `totalCredits` 与余额并等待同意，同意后追加 `--confirm`。
The standard workflow instructs the agent to invoke a potentially chargeable command without a prior quote and explicitly frames first-run behavior as delivering the report before discussing money. A request for analysis does not necessarily authorize an undisclosed charge, and recognizing the completed deduction afterward is too late to prevent it.
1. 运行 `check`，确认账户、邮箱验证状态和可用积点。
2. 用户要 VOC / 评论分析报告时，默认运行 `voc <ASIN> --site <站点>`，**不要再先跑一次报价**。
**返回里有 `autoConfirmed: true`（或直接带 `reportId` / 正文）就说明报告已经生成并扣点了**
（1.5.0：新用户首次体验直接出结果，用户先拿到报告再谈钱）。
此时把报告讲给用户，并转述 `charges` — 本次采集扣了多少、分析扣了多少、合计多少、扣后还剩多少。
**不要在拿到结果后再补问「要不要生成」，也不要再回头补一次报价。**
This instruction explicitly permits initial paid generations without an amount ceiling when the server marks them auto-confirmable. Although the user may request a report, the provider's first-run policy does not establish informed authorization to consume an unspecified quantity of credits.
- **价格一律以服务端本次报价为准**（`analysis/quote` 与 `collect` 报价返回的 `credits` /
`totalCredits`）。文档与示例里出现的任何单价、页数、合计都只是演示，后台可调，
**不要凭记忆或旧文档报数，也不要把示例价当成承诺价。**
- 报价返回 `autoConfirm: true` 时直接生成，不要再问「要不要」。
生成后一句话交代本次实际扣了多少、扣后余额（读 `charges` 字段）。
1.5.0 起服务端对新用户前几次付费生成不看金额上限：新用户验证邮箱后只给一个 ASIN，就一次性出报告。
- 用户说「以后别问了 / 50 以内直接做」→ 运行 `autoconfirm 50`；说「以后每次先问我」→ `autoconfirm off`；
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- 报价返回 `autoConfirm: true` 时直接生成，不要再问「要不要」。
生成后一句话交代本次实际扣了多少、扣后余额（读 `charges` 字段）。
1.5.0 起服务端对新用户前几次付费生成不看金额上限：新用户验证邮箱后只给一个 ASIN，就一次性出报告。
- 用户说「以后别问了 / 50 以内直接做」→ 运行 `autoconfirm 50`；说「以后每次先问我」→ `autoconfirm off`；
说「恢复默认」→ `autoconfirm default`。这是唯一需要你代用户设置的东西，设完复述一句当前规则。
- 报价需要确认时，只说两个数：这次多少积点（取报价返回的 `credits` / `totalCredits`，
**不要自己算、不要写死单价**）、余额多少，然后等用户一个「好」。单价与页数由后台配置决定，
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- 报价返回 `autoConfirm: true` 时直接生成，不要再问「要不要」。
生成后一句话交代本次实际扣了多少、扣后余额（读 `charges` 字段）。
1.5.0 起服务端对新用户前几次付费生成不看金额上限：新用户验证邮箱后只给一个 ASIN，就一次性出报告。
- 用户说「以后别问了 / 50 以内直接做」→ 运行 `autoconfirm 50`；说「以后每次先问我」→ `autoconfirm off`；
说「恢复默认」→ `autoconfirm default`。这是唯一需要你代用户设置的东西，设完复述一句当前规则。
- 报价需要确认时，只说两个数：这次多少积点（取报价返回的 `credits` / `totalCredits`，
**不要自己算、不要写死单价**）、余额多少，然后等用户一个「好」。单价与页数由后台配置决定，
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
生成后一句话交代本次实际扣了多少、扣后余额（读 `charges` 字段）。
1.5.0 起服务端对新用户前几次付费生成不看金额上限：新用户验证邮箱后只给一个 ASIN，就一次性出报告。
- 用户说「以后别问了 / 50 以内直接做」→ 运行 `autoconfirm 50`；说「以后每次先问我」→ `autoconfirm off`；
说「恢复默认」→ `autoconfirm default`。这是唯一需要你代用户设置的东西，设完复述一句当前规则。
- 报价需要确认时，只说两个数：这次多少积点（取报价返回的 `credits` / `totalCredits`，
**不要自己算、不要写死单价**）、余额多少，然后等用户一个「好」。单价与页数由后台配置决定，
商品评论不够这么多页时只收实际采到的页数，差额自动退回（`pricingNote` 已写好这句）。不要罗列参数。
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
**不要自己算、不要写死单价**）、余额多少，然后等用户一个「好」。单价与页数由后台配置决定，
商品评论不够这么多页时只收实际采到的页数，差额自动退回（`pricingNote` 已写好这句）。不要罗列参数。
**新手（`check` 返回 `autoConfirm.mode` 为 `first_runs` / `free_small`，或问"然后呢"）**
- 报告讲完只推一个下一步，附接口返回的成本，不写死月费用。用户同意再 `schedule --set weekly`。
- 不解释命令名，不列功能清单。用户问「还能做什么」时按他的产品状态给一条建议，不超过三句。
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
1.5.0 起服务端对前几次付费生成不看 `autoConfirmMaxCredits`，该字段**不再作为首次体验的硬拦截**，
只保留用户自设阈值与余额校验。`sampleCap` / `degraded` 表示 Free 样本封顶与轻量模型。
`voc` / `analyze` 在 autoConfirm 命中时会直接生成，返回 `autoConfirmed: true`、
`charges`（collectionCredits / analysisCredits / totalCredits / balanceBefore / balanceAfter）与 `autoConfirmNote`，
并附 `web.report` / `web.product` 网页链接。
- `voc`: Markdown VOC 报告，SSE 聚合后在 `data.content`，并归档。