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 agentmods add skills/openclaw-commons/openclaw-skill-commons/api-testingnpx skills add openclaw-commons/openclaw-skill-commons --skill api-testinggit clone --depth 1 https://github.com/openclaw-commons/openclaw-skill-commonsWhat 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 | $0.00000 | $0.00478 |
| Opus 5 | $0.00000 | $0.00239 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
api-testing 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 2d ago.
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.
This is a copy
83% identical to anyhow-error — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Api Testing
测试和质量保证技能
📦 安装
npx clawhub@latest install api-testing
🚀 快速开始
# 使用默认配置
openclaw api-testing
# 查看帮助
openclaw api-testing --help
# 指定配置
openclaw api-testing --config ./config.yaml
📖 功能特性
- ✅ 完整的Api Testing功能
- ✅ 开箱即用的默认配置
- ✅ 详细的文档和示例
- ✅ 社区支持和持续更新
- ✅ 与其他技能无缝集成
📝 使用示例
基础用法
openclaw api-testing
高级用法
openclaw api-testing --verbose --output ./output
与其他技能组合
openclaw api-testing | openclaw task-decomposer
⚙️ 配置选项
| 选项 | 说明 | 默认值 |
|---|---|---|
--verbose |
详细输出模式 | false |
--output |
输出目录 | ./output |
--config |
配置文件路径 | ./config.yaml |
--help |
显示帮助信息 | - |
📚 相关技能
- git-essentials - Git 工作流指南
- github - GitHub CLI 交互
- task-decomposer - 任务分解工具
🤝 贡献
欢迎提交 Issue 和 Pull Request！
- GitHub: https://github.com/openclaw-commons/openclaw-skill-commons
- 文档：https://openclaw-commons.github.io/openclaw-skill-commons
📄 许可证
MIT License - 详见 LICENSE
版本: 1.0.0
作者: OpenClaw Community
最后更新: 2026-03-03
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.
- 2d ago First seen · 83 lines · 0 tokens per session scan A ccf02526a3fd
api-testing is a skill published in the GitHub repository openclaw-commons/openclaw-skill-commons (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 478 tokens. A static security scan graded it A with 0 findings. It is 83% identical to anyhow-error, differing in 20 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…