Security audit
Security checks for vulnerabilities and agentic risk
This upgrade-planning skill can spend credits without fresh approval and includes broader operations with inconsistent spending and recurring-cost controls.
Prefer a corrected upgrade-only package with consistent quote-before-charge controls. If using this version, set the account to ask before every charge, request manual collection for one-off tasks, and review competitor and monitoring schedules. Omitting --confirm does not guarantee a free preview.
scripts/ari.pyRead-only deepdive can silently become paid analysis
A user requesting a preview can incur analysis charges. For an absent main subscription, the output can also claim that no credits were charged despite the reachable paid request.
scripts/ari.pyRecurring paid collection changes lack an executable confirmation gate
Premature invocation can establish ongoing collection and consume account credits on subsequent runs without a technically enforced recurring-cost acceptance step.
The document combines an upgrade-only, explicitly confirmed workflow with general instructions to invoke paid VOC generation without prior pricing or confirmation under server-defined defaults. These contradictory instructions create a credible path to credit consumption outside the advertised authorization boundary, although the claimed absence of local CLI enforcement cannot be verified from this file alone.
The declared purpose describes evidence-based upgrade planning, but the supplied chunk exposes operational controls for recurring monitoring, including price acceptance. These persistent and potentially billable actions are materially broader than merely retrieving supporting evidence for a planning task and are not disclosed in the description. The chunk does not demonstrate sales forecasting, procurement, or automatic product modification.
Amazon evidence collection could support product-upgrade planning, but persistent weekly monitoring and acceptance of recurring refresh pricing introduce operational capabilities not disclosed by the planning-only description. These are more than incidental evidence-retrieval details. The chunk contains CLI usage examples rather than the implementation, so it does not establish that charges occurred or that any watch was actually created. It also shows no sales forecasting, procurement ordering, or automatic product modification.
The visible commands concern watch-service pricing and listing rather than analyzing Amazon product details and reviews for upgrade planning. These are separate, undeclared capabilities, with no demonstrated connection to the stated planning workflow. The underlying script is not supplied, so additional behavior or resource access cannot be established.
Monitoring data could support upgrade planning, but managing persistent weekly watches with explicit per-refresh price acceptance is a material capability beyond the declared evidence-based planning purpose. The snippet does not show sales forecasting, procurement, or automatic product modification. This assessment concerns the exposed commands; their underlying implementation is not supplied.
Collecting evidence can support upgrade planning, but configuring ongoing monitoring and potentially billable weekly collection is an additional operational capability not disclosed in the declared purpose. The supplied chunk demonstrates scheduling commands, not upgrade prioritization or validation-question planning. It does not demonstrate sales forecasting, purchasing, or automatic product modification.
所示命令提供监控服务的报价和列表查询能力，而非商品详情、评论证据分析或产品升级规划。描述未声明这些监控相关功能，片段也未体现它们与升级规划之间的支持关系。没有证据表明代码会采购下单、修改产品或执行销量预测。
The comparison workflow recommends binding competitors and states that binding triggers weekly collection, without establishing a separate recurring-cost quote and consent step for that binding. Approval of a one-time comparison should not implicitly authorize ongoing competitor collection and potential charges.
The supplied command targets alerts rather than the described product-evidence analysis and upgrade planning. This indicates a purpose mismatch, although the missing script implementation limits certainty. The snippet does not establish whether alerts are retrieved, configured, or delivered, nor does it demonstrate sales forecasting, purchasing, or automatic product changes.
The skill instructs the agent to generate an idle, previously quoted report in a later conversation despite the user never answering the quote. Combined with server-default auto-confirmation, this treats silence and historical interest as authorization for a potentially paid operation unrelated to the current request.
run_analysis promotes an absent --confirm into confirmation based on the server's autoConfirm field, contradicting the CLI's explicit-confirmation contract. The analogous VOC path can also submit paid collection and analysis without local confirmation, allowing unexpected credit consumption; deepdive inherits the analysis behavior.
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 包早于免确认修复，新注册的免费版用户仍会被要求先确认报价。
1.5.1 与当前官网下发的修复版一致，市场侧以新版本号覆盖旧包。
- 免确认只认服务端报价返回的 `autoConfirm`；采集报价扣除首次采集免费页；
非美国站首次采集可用赠送积点时不再提示「赠送积点不可用」（行为与修复后的 1.5.0 相同）。
- 命令、字段与计费规则不变，不提高最低支持版本。
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.
- 行为变更：新用户（注册并验证邮箱后）第一次要 VOC，只给 ASIN 即可（站点默认美国站），
`voc` 直接执行——自动补采集（默认 3 页）、生成报告、按服务端定价扣费并归档，
不再停在报价等确认。费用在报告返回的 `charges` 字段透明展示（采集/分析/合计/余额前后）。
- 免确认与否**只认服务端报价返回的 `autoConfirm` 布尔**：服务端策略前 N 次付费生成不看金额上限
（新用户赠送积点按设计覆盖「3 页采集 + 一份 VOC」）；用户自设阈值优先、显式要求「每次先问」
时仍先报价；余额不足不自动。客户端不再从 `autoConfirmNote` 文案或 `autoConfirmRemaining`
自行推断——文案匹配会把 Free 小额提示里的「先确认」误判成用户要求每次询问，恰好挡住新用户。
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` 字段透明展示（采集/分析/合计/余额前后）。
- 免确认与否**只认服务端报价返回的 `autoConfirm` 布尔**：服务端策略前 N 次付费生成不看金额上限
（新用户赠送积点按设计覆盖「3 页采集 + 一份 VOC」）；用户自设阈值优先、显式要求「每次先问」
时仍先报价；余额不足不自动。客户端不再从 `autoConfirmNote` 文案或 `autoConfirmRemaining`
自行推断——文案匹配会把 Free 小额提示里的「先确认」误判成用户要求每次询问，恰好挡住新用户。
- 采集报价同口径扣除服务端 `trialFreePages`（首次采集试用免费页），避免新用户被误报「积点不足」。
- 非美国站：服务端 `credits.gift` 策略下用户首次采集不限站点，`credits/balance` 返回 `giftAllSites`，
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` 字段透明展示（采集/分析/合计/余额前后）。
- 免确认与否**只认服务端报价返回的 `autoConfirm` 布尔**：服务端策略前 N 次付费生成不看金额上限
（新用户赠送积点按设计覆盖「3 页采集 + 一份 VOC」）；用户自设阈值优先、显式要求「每次先问」
时仍先报价；余额不足不自动。客户端不再从 `autoConfirmNote` 文案或 `autoConfirmRemaining`
自行推断——文案匹配会把 Free 小额提示里的「先确认」误判成用户要求每次询问，恰好挡住新用户。
- 采集报价同口径扣除服务端 `trialFreePages`（首次采集试用免费页），避免新用户被误报「积点不足」。
- 非美国站：服务端 `credits.gift` 策略下用户首次采集不限站点，`credits/balance` 返回 `giftAllSites`，
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.
为 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 auto-confirm rules include service-provided first-use allowances with no amount limit, not just user-configured spending thresholds. Treating those defaults as payment authorization allows credits to be consumed before the user sees or approves the cost, contradicting this specialized skill's explicit-confirmation requirement.
`voc <ASIN>`（没说站点就用默认的美国站，不要为此追问）。
命中服务端免确认规则（新用户首次体验不看金额 / 账户剩余免确认次数 / 用户自设阈值）且余额充足时，
**直接完成采集 + 生成 + 扣点并归档**，不再停在报价环节。绝不能描述成“先帮你问个价 / 只报价不扣点”。
免确认与否以返回里的 `autoConfirm` 为准，不要自己从提示文案里猜。
- 直接生成成功后，返回结果带 `charges`（采集扣点、分析扣点、合计、扣前/扣后余额）与 `autoConfirmNote`。
**先讲报告，再用一句话转述实际扣点**，不要在拿到结果后再补问「要不要生成」，也不要回头补一次报价。
- 只有在返回 `confirmationRequired: true` 时（余额不足、或用户自行设置了“每次先问”）
A server-returned autoConfirm flag indicates service policy, but does not itself establish informed user authorization. The surrounding instructions nevertheless use it to permit immediate deduction, including first-use policies without a monetary cap.
命中服务端免确认规则（新用户首次体验不看金额 / 账户剩余免确认次数 / 用户自设阈值）且余额充足时，
**直接完成采集 + 生成 + 扣点并归档**，不再停在报价环节。绝不能描述成“先帮你问个价 / 只报价不扣点”。
免确认与否以返回里的 `autoConfirm` 为准，不要自己从提示文案里猜。
- 直接生成成功后，返回结果带 `charges`（采集扣点、分析扣点、合计、扣前/扣后余额）与 `autoConfirmNote`。
**先讲报告，再用一句话转述实际扣点**，不要在拿到结果后再补问「要不要生成」，也不要回头补一次报价。
- 只有在返回 `confirmationRequired: true` 时（余额不足、或用户自行设置了“每次先问”）
才报出 `totalCredits` 与余额并等待同意，同意后追加 `--confirm`。
The standard workflow deliberately invokes a potentially charging command before quoting, then discloses charges only after completion. Receiving report content or a report ID confirms an outcome, not prior authorization, so this sequence can spend credits without informed approval.
1. 运行 `check`，确认账户、邮箱验证状态和可用积点。
2. 用户要 VOC / 评论分析报告时，默认运行 `voc <ASIN> --site <站点>`，**不要再先跑一次报价**。
**返回里有 `autoConfirmed: true`（或直接带 `reportId` / 正文）就说明报告已经生成并扣点了**
（1.5.0：新用户首次体验直接出结果，用户先拿到报告再谈钱）。
此时把报告讲给用户，并转述 `charges` — 本次采集扣了多少、分析扣了多少、合计多少、扣后还剩多少。
**不要在拿到结果后再补问「要不要生成」，也不要再回头补一次报价。**
The manifest limits the skill to planning product upgrades from product details and review evidence. These instructions instead invoke paid keyword analysis to produce advertising terms, negative keywords, competitor brand terms, and a backend Search Terms string, and proactively promote advertising use after reports. This is a distinct marketing capability rather than an implementation detail of upgrade planning.
This passage explicitly permits initial paid generations without an amount ceiling and suppresses a confirmation question. A generic request to analyze an ASIN does not establish acceptance of an undisclosed service charge, especially when the specialized entry point promises explicit confirmation.
- **价格一律以服务端本次报价为准**（`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.
生成后一句话交代本次实际扣了多少、扣后余额（读 `charges` 字段）。
1.5.0 起服务端对新用户前几次付费生成不看金额上限：新用户验证邮箱后只给一个 ASIN，就一次性出报告。
- 用户说「以后别问了 / 50 以内直接做」→ 运行 `autoconfirm 50`；说「以后每次先问我」→ `autoconfirm off`；
说「恢复默认」→ `autoconfirm default`。这是唯一需要你代用户设置的东西，设完复述一句当前规则。
- 报价需要确认时，只说两个数：这次多少积点（取报价返回的 `credits` / `totalCredits`，
**不要自己算、不要写死单价**）、余额多少，然后等用户一个「好」。单价与页数由后台配置决定，
商品评论不够这么多页时只收实际采到的页数，差额自动退回（`pricingNote` 已写好这句）。不要罗列参数。