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 commands/dodobrands/ai-hub/testopsgit clone --depth 1 https://github.com/dodobrands/ai-hubWrote 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/dodobrands/ai-hub/testops)<a href="https://agentmods.dev/commands/dodobrands/ai-hub/testops"><img src="https://agentmods.dev/badge/commands/dodobrands/ai-hub/testops.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.00028 | $0.00981 |
| Opus 5 | $0.00014 | $0.00491 |
| Sonnet 5 | $0.00006 | $0.00196 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
testops 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TestOps CLI — работа с Allure TestOps
Выполни запрос к Allure TestOps API через скрипты интеграции.
Переменные окружения
Скрипты читают из .env в корне репозитория:
TESTOPS_URL— базовый URL инстанса (напр.https://your-company.qatools.cloud)TESTOPS_TOKEN— персональный API-токен (Profile → API Tokens)
Скрипты
Низкоуровневый (произвольный API-вызов)
./integrations/testops/scripts/testops.sh <METHOD> <endpoint> [json_body]
# Пример: ./integrations/testops/scripts/testops.sh GET /project?page=0&size=10
Высокоуровневый (подкоманды)
./integrations/testops/scripts/testops-api.sh <command> [args...]
Доступные подкоманды
| Команда | Описание | Пример |
|---|---|---|
projects [query] |
Поиск проектов | testops-api.sh projects "MyService" |
testcases <projectId> [rql] |
Поиск тест-кейсов (AQL) | testops-api.sh testcases 2298 'name~="Login"' |
testcase <id> |
Обзор тест-кейса | testops-api.sh testcase 12345 |
testcase-scenario <id> |
Шаги тест-кейса | testops-api.sh testcase-scenario 12345 |
testcase-history <id> |
История запусков тест-кейса | testops-api.sh testcase-history 12345 |
launches <projectId> [rql] |
Поиск запусков (AQL) | testops-api.sh launches 2298 'name~="Regression"' |
launch <id> |
Детали запуска | testops-api.sh launch 132069 |
launch-stats <id> |
Статистика запуска | testops-api.sh launch-stats 132069 |
defects <projectId> [name] |
Поиск дефектов | testops-api.sh defects 2298 |
defect <id> |
Детали дефекта | testops-api.sh defect 456 |
jobs [projectId] |
Поиск джобов | testops-api.sh jobs 2298 |
job <id> |
Детали джоба | testops-api.sh job 789 |
testplans <projectId> [name] |
Поиск тест-планов | testops-api.sh testplans 2298 |
testplan <id> |
Детали тест-плана | testops-api.sh testplan 101 |
run-testplan <id> <name> |
Запуск тест-плана | testops-api.sh run-testplan 101 "Release 1.0" |
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.
- yesterday First seen · 76 lines · 28 tokens per session scan A 5bf8e83ebc67
testops is a command published in the GitHub repository dodobrands/ai-hub (6 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 981 once invoked, about $0.0001 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-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.