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.
git clone --depth 1 https://github.com/csmar432/finai-researchWrote 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/csmar432/finai-research/test)<a href="https://agentmods.dev/commands/csmar432/finai-research/test"><img src="https://agentmods.dev/badge/commands/csmar432/finai-research/test/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/commands/csmar432/finai-research/test"><img src="https://agentmods.dev/badge/commands/csmar432/finai-research/test.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.00000 | $0.00291 |
| Opus 5.5 | $0.00000 | $0.00116 |
| Sonnet 5.5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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 1mo 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
test — 运行测试
description: 运行 pytest 测试套件，可选按关键字过滤
arguments
[pattern](可选): pytest 关键字过滤模式
描述
运行项目测试套件。
等价于：
pytest tests/ -v -k "<pattern>"
示例
/test # 运行全部测试
/test regression # 只运行回归相关测试
/test did # 只运行 DID 相关测试
/test data_fetcher # 只运行数据获取测试
/test checkpoint # 只运行断点续传测试
/test -k "did or iv" # 运行 DID 或 IV 测试
测试覆盖
| 测试文件 | 覆盖范围 |
|---|---|
tests/test_checkpoint.py |
断点续传管理 |
tests/test_event_monitor.py |
事件监控系统 |
tests/test_demo_research_report.py |
研报生成流水线 |
tests/test_llm_gateway.py |
LLM 网关与路由 |
tests/test_ollama_provider.py |
Ollama 本地模型 |
tests/test_econometrics.py |
计量经济学方法 |
tests/test_data_cache.py |
数据缓存 |
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.
- 1mo ago First seen · 41 lines · 0 tokens per session scan A 4b36fea0e45c
test is a command published in the GitHub repository csmar432/finai-research (108 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 291 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
tdd
Enforce test-driven development workflow. Scaffold interfaces, generate tests FIRST, then implement minimal code to pass. Ensure 80%+ coverage.
refactor-clean
Safely identify and remove dead code with test verification.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
playwright-cli
Automate browser interactions and inspect or test web pages through Playwright commands. Use when the task requires deterministic browser navigation, screenshots, selectors, or Playwright-test work. For a full local-webapp test workflow, use $webapp-testing.
test-iterate-loop
Autonomously diagnose a codebase, apply minimal fixes, and rerun tests until they pass or a real blocker is reached. Use when the user explicitly requests an iterative fix-until-green loop across Python, R, Julia, or HPC workflows.
sandbox-test
Guide through Straddle sandbox testing scenarios.