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.
npx skills add rojim666/SztuCode --skill weixinpay-feedbackgit clone --depth 1 https://github.com/rojim666/SztuCodeWrote 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/skills/rojim666/sztucode/weixinpay-feedback)<a href="https://agentmods.dev/skills/rojim666/sztucode/weixinpay-feedback"><img src="https://agentmods.dev/badge/skills/rojim666/sztucode/weixinpay-feedback/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rojim666/sztucode/weixinpay-feedback"><img src="https://agentmods.dev/badge/skills/rojim666/sztucode/weixinpay-feedback.svg" alt="Reviewed on agentmods" width="80" 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.00115 | $0.01948 |
| Opus 5 | $0.00057 | $0.00974 |
| Sonnet 5 | $0.00023 | $0.00390 |
| Haiku 4.5 | $0.00012 | $0.00195 |
Grade A, and why
weixinpay-feedback 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 today.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
微信支付AI专属卡问题反馈
功能描述
将用户在使用微信支付AI专属卡过程中遇到的使用异常反馈给微信支付团队,包括:
- 无法开通或绑定微信支付AI专属卡
- 无法发起支付
- 支付失败或支付无响应
- 支付结果查询异常
用户也可以选择通过用户反馈收集表手动提交反馈:微信支付AI专属卡问题反馈。
适用场景
用户在使用微信AI支付/AI专属卡过程中遇到无法通过重试或常规引导解决的问题、并希望反馈时使用。按问题类型选择反馈方式:
- 开通 / 绑定过程的问题(如开通失败、绑定不上)直接展示反馈收集表链接引导手动提交,不调用工具(见「开通/绑定问题的反馈方式」)
- 支付 / 管理问题(如支付失败、扣款异常、余额或 AI专属卡管理问题)调用工具
mcp__weixinpay__weixinpay_feedback反馈(见执行流程) - 用户直接要给微信支付反馈问题(未明确属于上面哪类)默认走工具反馈
典型情况:
- 绑定、开通流程反复失败或卡住
- 支付点击后无反应、扣款失败或返回未知错误
- 支付技能返回未知错误码或异常输出
- 用户主动要求反馈上述绑定、开通或支付问题
连续报错主动引导:当同一环节(开通 / 绑定 / 支付 / 查询)出现连续或反复报错、重试后仍失败时,即使用户没有明确说"反馈",也应主动提示可通过本技能将问题上报给微信支付团队,并询问用户是否愿意反馈。
开通/绑定问题的反馈方式
开通或绑定过程中的问题(这类用户通常尚未绑定成功,无法通过工具上报),不调用工具,直接向用户展示反馈收集表链接,引导其手动提交:
你可以通过用户反馈收集表提交问题反馈:https://doc.weixin.qq.com/forms/AJEAIQdfAAoAHYAggbdAFwCNVtpxmtQAf
不适用场景
- 问题可以通过重试或常规引导解决
- 用户只是普通咨询(如"怎么支付"、"你付好了么"、"你搞定了么")
- 用户是要开通或绑定微信支付AI专属卡,应使用
weixinpay-register技能 - 开发者或商户接入问题(商户号、API 证书、回调配置等)
安全性与设计说明
本技能由微信支付官方提供,用于收集用户反馈以改进产品体验。
数据收集说明
收集范围:
- 用户在当前会话中主动描述的问题内容(
description参数) - 用户明确同意后,可上传当天运行日志(
uploadLogs参数)
不会上传:
- 用户凭证等敏感信息
数据发送:
- 数据仅发送至微信支付官方服务
- 不发送至第三方服务器
- 反馈用于问题排查和产品改进
行为边界:
- 每轮提交反馈前,都必须先询问用户是否同意上传当天运行日志
- 不得复用上一轮的同意或拒绝结果;重试、补充反馈、再次提交都必须重新征求用户意见
- 问题描述只来自用户在当前会话中主动提供的内容,不读取本地文件、剪贴板、截图或其他外部来源
入参说明
| 参数 | 类型 | 必填 | 说明 |
|---|---|---|---|
description |
string | 是 | 用户在当前会话中主动描述的问题内容,整理后传入 |
uploadLogs |
boolean | 是 | 是否随反馈上传当天运行日志。必须先询问用户意愿后再决定 |
执行流程
以下流程(调用工具)用于支付 / 管理问题,以及用户直接要反馈时的默认路径;开通 / 绑定问题直接走「开通/绑定问题的反馈方式」展示链接,不走此流程。
Step 1:收集问题信息
在调用工具前,先整理问题描述。问题描述应包含:
- 用户遇到了什么问题
- 问题发生在哪个环节(开通 / 绑定 / 支付 / 查询状态)
- 具体的错误信息(如有)
Step 2:征求日志上传同意
每一轮调用工具前,都必须向用户确认是否同意上传当天运行日志。
参考话术:
我可以帮你把这个问题反馈给微信支付团队。为了便于排查,是否同意一并上传支付工具当天的运行日志?
如果不同意,我也可以只提交你描述的问题内容。
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.
- today First seen · 172 lines · 115 tokens per session scan A de1f797a31e6
weixinpay-feedback is a skill published in the GitHub repository rojim666/SztuCode (64 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 1,948 once invoked, about $0.0006 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-09-12.
Other skills, from other repositories
copperhead
Change or verify a KiCad project through copperhead's gated pipeline. Use whenever a task touches .kicadsch or .kicadpcb files, a schematic, a PCB layout, a netlist, ERC/DRC, a BOM, or hardware design docs — instead of editing those files directly.
wallet
Pay x402-payable endpoints in USDC from the sandbox wallet via the wallet CLI, under the owner's spending policy. Use when an API answers 402 Payment Required with an x402 challenge: check the price, then ask; the owner approves each payment outside their auto-approve band.
saas-economics-efficiency-metrics
Evaluate SaaS unit economics and capital efficiency. Use when deciding whether the business can scale efficiently or needs correction.
tura
Work in the Tura agent-runtime repository. Use for Tura architecture, Rust backend, GUI/TUI, prompts, commands, providers, sessions, documentation, tests, packaging, and release work in this directory.
business-health-diagnostic
Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.
feature-investment-advisor
Evaluate feature investments using revenue impact, cost structure, ROI, and strategy. Use when deciding whether a feature deserves investment.