Security audit
Security checks for vulnerabilities and agentic risk
This mobile-listing tool includes broader paid and recurring account actions, and a preview command can unexpectedly consume credits.
Prefer a corrected version with enforced mobile-only scope and reliable preview behavior. If used, set the account to ask before each charge, use the dedicated quote command for price checks, and choose manual collection unless you explicitly approve recurring costs.
scripts/ari.pyPreview-only deepdive can execute a paid analysis without --confirm
A user requesting a preview can consume credits unexpectedly. When no main-product subscription is found and --confirm was supplied, the output can additionally claim that execution was downgraded to a quote without charging, despite the helper having automatically executed.
The competitor-binding instructions state that binding starts weekly collection, but do not locally require separate approval for that recurring side effect. General schedule-consent rules mitigate the issue, yet a user authorizing a one-time comparison could still receive an unintended persistent collection relationship.
The narrow mobile-diagnosis description conflicts with extensive instructions for paid VOC execution, advertising analysis, and persistent monitoring. The final listing/mobile restriction mitigates this, but contradictory instructions—including a claim that this is an unrestricted general entry point—can lead the agent to select broader, charge-incurring workflows.
Creating and resuming recurring watches changes persistent account state and authorizes future charges outside the declared diagnostic scope. The documented price quotation and explicit-consent requirements reduce unauthorized-billing risk, but do not resolve the conflicting scope instructions.
This duplicates the recurring-watch scope issue: a presentation-diagnosis skill includes instructions to create persistent, potentially billable monitoring relationships. Explicit consent and ownership checks are meaningful safeguards, but the contradictory capability boundaries still permit workflow drift.
This is another instance of the recurring-watch scope vulnerability, not an independent exploit. Creating or resuming watches can authorize future spending outside the mobile-only contract, although the explicit price-consent requirements substantially limit the risk.
Watch pricing and watch-list management are not disclosed in the mobile-expression diagnostic purpose, and the snippet does not show any product-detail, review-evidence, or mobile-readability analysis. Although the underlying script is not provided, the supplied commands expose materially different functionality rather than a clearly supporting implementation detail.
The supplied command requests a category leaderboard based on negative-review rate. That is a materially different analytical task from examining a listing's mobile presentation and comprehension barriers. Although reviews are relevant to the declared purpose, ranking a product category by negative-review rate is not itself a mobile-expression diagnostic. The CLI implementation is not supplied, so the confirmation flag does not establish any additional side effects.
The supplied commands concern watch digests, events, and historical series rather than product-detail and review-based mobile readability analysis. Nothing in the chunk connects these monitoring operations to the declared diagnostic workflow. The underlying ARI implementation is not supplied, so its specific data sources and any additional effects cannot be determined.
Recurring collection introduces continuing charges and persistent account changes beyond a one-time mobile diagnosis. Although the text requires consent and manual scheduling when recurrence is not authorized, a weekly default and conflicting general-purpose workflows increase the chance of unintended activation.
The supplied commands expose monitoring-related capabilities that are not disclosed in the mobile-expression diagnostic description. The chunk contains no product-detail or review analysis connecting these commands to that purpose. It demonstrates watch inspection, but does not establish watch creation, inventory operations, advertising, or automatic publishing.
The supplied invocation explicitly selects '--type compare' and supplies '--competitor', indicating a competitive comparison workflow not disclosed in the mobile-only description. Nothing in the visible command establishes a mobile-readability focus. The underlying script is not supplied, so its data access and downstream effects cannot be verified; there is no visible evidence of advertising, inventory management, or automatic publishing.
The supplied command targets alerts rather than an identifiable Listing readability analysis workflow. Alerts are not described in the declared purpose. However, the implementation of scripts/ari.py is absent, so the precise alert behavior, resource access, and possible side effects cannot be verified.
run_analysis changes confirm from false to true when the server returns a truthy autoConfirm value, then invokes the chargeable endpoint. Consequently, analyze and deepdive can spend credits without the explicit flag promised by the module; deepdive's attempted downgrade to quote-only can also be defeated by this 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.
为 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.
不再停在报价等确认。费用在报告返回的 `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.
- 能力层收窄：44 个专属包不再只是「声明窄」，包体 `scripts/ari.py` 同时按各自契约裁剪。
构建期用 AST 删除文档未承诺的命令、它们的解析器注册块，以及只被它们引用的辅助函数与
常量；专属包因此不再包含 `export`（任意路径写文件）、`autoconfirm`（撤销逐次确认）、
`workbench`（改写差评处理状态）、`alerts`（标记预警已读）、`competitors`、`schedule`、
`voc` / `analyze` / `charts` / `deepdive` 等母版命令。
- 新增运行期兜底闸：专属包在包内写入 `allowedCommands` 白名单，`ari.py`
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.
p = sub.add_parser("check", parents=[common], help="验证 Key、账户和积点余额")
p.set_defaults(fn=cmd_check)
p = sub.add_parser("autoconfirm", parents=[common],
help="免确认阈值：autoconfirm 50 / autoconfirm off / autoconfirm default；不带参数查看")
p.add_argument("value", nargs="?", default="")
p.set_defaults(fn=cmd_autoconfirm)
Without declared permissions the skill's intent is opaque and cannot be validated.
The instructions permit immediate credit deductions based on server-defined first-use exemptions that explicitly have no amount limit. A server eligibility flag is not proof of informed user spending authorization, and this contradicts the specialized skill's requirement to quote and obtain explicit confirmation.
`voc <ASIN>`（没说站点就用默认的美国站，不要为此追问）。
命中服务端免确认规则（新用户首次体验不看金额 / 账户剩余免确认次数 / 用户自设阈值）且余额充足时，
**直接完成采集 + 生成 + 扣点并归档**，不再停在报价环节。绝不能描述成“先帮你问个价 / 只报价不扣点”。
免确认与否以返回里的 `autoConfirm` 为准，不要自己从提示文案里猜。
- 直接生成成功后，返回结果带 `charges`（采集扣点、分析扣点、合计、扣前/扣后余额）与 `autoConfirmNote`。
**先讲报告，再用一句话转述实际扣点**，不要在拿到结果后再补问「要不要生成」，也不要回头补一次报价。
- 只有在返回 `confirmationRequired: true` 时（余额不足、或用户自行设置了“每次先问”）
This duplicates the automatic-billing issue: autoConfirm can represent provider-defined exemptions rather than user-approved spending limits. Following it can consume credits before the user sees the price, despite the mobile workflow's explicit-confirmation requirement.
命中服务端免确认规则（新用户首次体验不看金额 / 账户剩余免确认次数 / 用户自设阈值）且余额充足时，
**直接完成采集 + 生成 + 扣点并归档**，不再停在报价环节。绝不能描述成“先帮你问个价 / 只报价不扣点”。
免确认与否以返回里的 `autoConfirm` 为准，不要自己从提示文案里猜。
- 直接生成成功后，返回结果带 `charges`（采集扣点、分析扣点、合计、扣前/扣后余额）与 `autoConfirmNote`。
**先讲报告，再用一句话转述实际扣点**，不要在拿到结果后再补问「要不要生成」，也不要回头补一次报价。
- 只有在返回 `confirmationRequired: true` 时（余额不足、或用户自行设置了“每次先问”）
才报出 `totalCredits` 与余额并等待同意，同意后追加 `--confirm`。
The default workflow instructs the agent to skip quotation and invoke a command that may already collect data and deduct credits before returning. Reporting charges afterward provides transparency but cannot substitute for prior authorization.
1. 运行 `check`，确认账户、邮箱验证状态和可用积点。
2. 用户要 VOC / 评论分析报告时，默认运行 `voc <ASIN> --site <站点>`，**不要再先跑一次报价**。
**返回里有 `autoConfirmed: true`（或直接带 `reportId` / 正文）就说明报告已经生成并扣点了**
（1.5.0：新用户首次体验直接出结果，用户先拿到报告再谈钱）。
此时把报告讲给用户，并转述 `charges` — 本次采集扣了多少、分析扣了多少、合计多少、扣后还剩多少。
**不要在拿到结果后再补问「要不要生成」，也不要再回头补一次报价。**
The workflow explicitly routes advertising-keyword requests into paid analysis despite the advertised exclusion of advertising and the final mobile-only restriction. This creates an instruction-level scope boundary failure, although quotation and confirmation reduce the likelihood of unauthorized spending.