Borrowing it
Nothing to install: this file belongs to loonghao/auroraview. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/loonghao/auroraview/main/.codebuddy/commands/mcp-quick-test.mdgit clone --depth 1 https://github.com/loonghao/auroraviewWrote 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/commands/loonghao/auroraview/mcp-quick-test)<a href="https://agentmods.dev/commands/loonghao/auroraview/mcp-quick-test"><img src="https://agentmods.dev/badge/commands/loonghao/auroraview/mcp-quick-test.svg" alt="Measured on agentmods" 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.00000 | $0.00582 |
| Opus 5 | $0.00000 | $0.00291 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
mcp-quick-test 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 8d 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.
What it actually says
快速测试 auroraview-dev MCP 服务器的所有核心功能。
测试流程
请依次执行以下测试:
- 获取项目信息 - 调用
get_project_info验证 MCP 服务器正常运行 - 获取可用示例 - 调用
get_samples列出所有可用示例 - 发现实例 - 调用
discover_instances查看运行中的 AuroraView 实例 - 启动 Gallery - 如果没有实例，调用
run_gallery启动 Gallery (端口 9222) - 连接实例 - 调用
connect(port=9222)连接到 Gallery - 截图验证 - 调用
take_screenshot截图确认连接成功 - 获取页面快照 - 调用
get_snapshot获取页面结构 - 测试 API - 调用
list_api_methods和call_api测试 Python API 桥接
测试报告
测试完成后，生成测试报告:
| 步骤 | 工具 | 状态 | 结果/问题 |
|---|---|---|---|
| 1 | get_project_info | ? | |
| 2 | get_samples | ? | |
| ... | ... | ... |
问题处理
如果发现问题，请按以下格式总结:
## Issue Summary
**Type**: Bug / Missing Feature / Design Flaw
**Severity**: Critical / High / Medium / Low
**Component**: affected file/module
**Problem**: Brief description
**Root Cause**: Why this happens
**Impact**: What is affected
然后等待开发者确认如何处理:
- 在当前分支修复 - 小改动，直接修复
- 创建新分支 - 较大改动，需要隔离 (基于 remote main)
- 创建 GitHub Issue - 记录待办，暂不处理
- 创建 RFC 提案 - 设计变更，需要讨论
请选择: [1/2/3/4]
创建新分支流程 (选项 2)
# 1. 获取最新的 remote main
git fetch origin main
# 2. 基于 remote main 创建新分支
git checkout -b fix/issue-name origin/main
# 3. 修改代码...
# 4. 提交并推送
git add -A
git commit -m "fix: description"
git push -u origin fix/issue-name
# 5. 创建 PR (可选)
gh pr create --title "fix: description" --body "..."
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.
- 8d ago First seen · 72 lines · 0 tokens per session scan A 30a7538305f7
mcp-quick-test is a command published in the GitHub repository loonghao/auroraview (44 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 582 tokens. 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-08-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.