test

A command that runs the project's full automated test process, including unit tests, a build, and checks against a running FIT service.

In plain words
What is it for?
Use it before committing changes to build the project, start the service, check health and plugin endpoints, verify the Swagger documentation page, and generate a test report.
Why use it?
It brings the main checks into one repeatable run and leaves test and service logs when something fails.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/modelengine-group/fit-framework/test
Clone the repo
git clone --depth 1 https://github.com/ModelEngine-Group/fit-framework

Made for: Claude Code.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 532 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00007 $0.00532
Opus 5 $0.00003 $0.00266
Sonnet 5 $0.00001 $0.00106
Haiku 4.5 $0.00001 $0.00053

Measured yesterday against content hash 9773a86aa06a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

.claude/commands/test.md · 61 lines

What it actually says

Test Command

功能说明

执行完整的测试流程,包括单元测试、构建验证和集成测试。

用法:

  • /test - 执行完整测试流程

执行方式:

使用自动化测试脚本执行完整的测试流程:

./.agents/scripts/run-test.sh

测试流程包括:

  1. 清理构建产物 - 删除之前的 build 目录
  2. 执行单元测试和构建 - 运行 mvn clean install 执行全量单元测试
  3. 创建动态插件目录 - 创建 dynamic-plugins 目录
  4. 启动 FIT 服务 - 使用 build/bin/fit start 启动服务
  5. 验证健康检查接口 - 访问 /actuator/plugins 接口
  6. 验证 Swagger 文档 - 访问 /openapi.html 页面
  7. 清理测试环境 - 停止服务并删除构建产物

测试报告:

脚本会自动生成测试报告,包含:

  1. ✅/✗ 单元测试结果
  2. ✅/✗ 构建状态
  3. ✅/✗ FIT 服务启动状态
  4. ✅/✗ 健康检查接口响应
  5. ✅/✗ Swagger 文档页面可访问性

日志输出:

所有测试日志保存在 .ai-workspace/logs/ 目录(已被 git 忽略):

  • maven-build-{timestamp}.log - Maven 构建日志
  • fit-server-{timestamp}.log - FIT 服务启动日志

下一步:

测试通过后,使用以下命令提交代码:

  • Claude Code / OpenCode: /commit
  • Gemini CLI: /fit:commit
  • Codex CLI: /prompts:fit-commit

注意事项:

  1. 端口冲突:确保 8080 端口未被占用
  2. 权限配置:测试脚本已在 .claude/settings.json 中配置自动授权
  3. 完全自动化:整个测试流程无需手动确认,自动执行所有步骤
  4. 日志保留:测试日志在清理时会被保留在 .ai-workspace/logs/ 目录
Changes

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.

  1. yesterday First seen · 61 lines · 7 tokens per session scan A 9773a86aa06a

Subscribe to this mod's changes

test is a command published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 532 once invoked, about $0.0000 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-08-30.