allure-testops

allure-testops is a skill for Claude Code, Codex from iampopovich/allure-testops-mcp. It costs 116 tokens per session (3,346 once invoked), scanned A, original, MIT.

An integration guide for Allure TestOps, a tool for managing test cases and test results. It covers finding, creating, and updating cases, running manual test launches, and reviewing failed results and defects.

In plain words
What is it for?
Use it to manage test cases, steps, expected results, tags, links, manual launches, failed results, and defects in Allure TestOps.
Why use it?
It reduces mistakes when an external test-management tool reports success without actually saving a change. It requires checking each write by reading the result back.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions Claude Code.

Good fit Use it to manage test cases, steps, expected results, tags, links, manual launches, failed results, and defects in Allure TestOps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/iampopovich/allure-testops-mcp/allure-testops
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.

Any agent
npx skills add iampopovich/allure-testops-mcp --skill allure-testops
Clone the repo
git clone --depth 1 https://github.com/iampopovich/allure-testops-mcp

Made for: Claude Code, Codex.

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

agentmods badge for allure-testops

README.md
[![agentmods](https://agentmods.dev/badge/skills/iampopovich/allure-testops-mcp/allure-testops/github.svg)](https://agentmods.dev/skills/iampopovich/allure-testops-mcp/allure-testops)
Your own site
<a href="https://agentmods.dev/skills/iampopovich/allure-testops-mcp/allure-testops"><img src="https://agentmods.dev/badge/skills/iampopovich/allure-testops-mcp/allure-testops/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.

agentmods 80×15 button for allure-testops

Your own site · 80×15
<a href="https://agentmods.dev/skills/iampopovich/allure-testops-mcp/allure-testops"><img src="https://agentmods.dev/badge/skills/iampopovich/allure-testops-mcp/allure-testops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,346 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00116 $0.03346
Opus 5.5 $0.00046 $0.01338
Sonnet 5.5 $0.00023 $0.00669
Haiku 4.5 $0.00012 $0.00335

Measured 3d ago against content hash 788903c16ca4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

allure-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 3d 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.

skills/allure-testops/SKILL.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Allure TestOps

This skill drives the allure-testops-mcp MCP server. The server exposes ~120 tools. The rules below come from production use: several tools succeed (200 OK) while silently writing nothing, or write something you did not ask for. Follow the workflows exactly and verify every write with a read-back.

Setup (if the tools are not available)

If no allure-testops tools (find_test_cases, get_test_case, …) are present, the MCP server is not installed. Tell the user to add it to their MCP client config and restart the client:

{
  "mcpServers": {
    "allure-testops": {
      "command": "npx",
      "args": ["-y", "allure-testops-mcp"],
      "env": {
        "ALLURE_TESTOPS_URL": "https://your-instance.example.com",
        "ALLURE_TOKEN": "<user API token from Allure profile>",
        "ALLURE_PROJECT_ID": "<optional default project id>"
      }
    }
  }
}

Claude Code shortcut: claude mcp add allure-testops -e ALLURE_TESTOPS_URL=... -e ALLURE_TOKEN=... -- npx -y allure-testops-mcp

Never ask the user to paste their token into the chat; they put it in the config themselves.

Data flow. This skill contains instructions only: no scripts, no network calls, no environment-variable reads. The config above is an example the user fills in for their own MCP client. The MCP server reads ALLURE_TESTOPS_URL and ALLURE_TOKEN from that config and talks only to the user's own Allure TestOps instance at that URL; nothing is sent anywhere else.

"No such tool available" for one specific tool (while other Allure tools work) usually means the calling agent or subagent has a restricted tool allowlist, not that the server lacks the tool. Check the agent's tools: grant before concluding a capability is missing, and never invent a workaround (such as writing steps into description) on that basis.

Several Allure servers configured (e.g. allure-testops for production and allure-testops-local for a dev instance): use the one the user's team treats as default, and switch only when the user explicitly names the other.

Read the full file on GitHub · 158 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 3d ago First seen · 158 lines · 116 tokens per session scan A 788903c16ca4

Subscribe to this mod's changes

allure-testops is a skill published in the GitHub repository iampopovich/allure-testops-mcp (2 stars, last pushed 3d ago), licensed MIT. It adds 116 tokens to every session and 3,346 once invoked, about $0.0005 per session on Opus 5.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-10-13.

Related

Other skills, from other repositories

live-audit

Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…

Grinv/steam-games-mcp · 83 tokens

prompt-check

Live-test every MCP Prompt in src/tools/prompts.ts through the real MCP protocol (not a static read) across every argument combination. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.

Grinv/steam-games-mcp · 54 tokens

lastest

Run visual regression tests, review screenshot diffs, and manage baselines on a Lastest instance via the @lastest/mcp-server MCP tools.

las-team/lastest · 33 tokens

api-testing

Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.

cyanheads/pubmed-mcp-server · 46 tokens

add-test

Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.

cyanheads/pubmed-mcp-server · 41 tokens

lore-onboard

First-time setup wizard for LoreConvo. Verifies the MCP server is connected, the database is accessible, hooks are configured, and runs a test save/load cycle. Use when the user says "set up loreconvo", "onboard", "/lore-onboard", "verify loreconvo", "test loreconvo setup", or after first installing the plugin.

labyrinth-analytics/loreconvo · 81 tokens