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 skills add uarlouski/testrail-mcp-server --skill testrail-qagit clone --depth 1 https://github.com/uarlouski/testrail-mcp-serverWrote 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/skills/uarlouski/testrail-mcp-server/testrail-qa)<a href="https://agentmods.dev/skills/uarlouski/testrail-mcp-server/testrail-qa"><img src="https://agentmods.dev/badge/skills/uarlouski/testrail-mcp-server/testrail-qa/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/skills/uarlouski/testrail-mcp-server/testrail-qa"><img src="https://agentmods.dev/badge/skills/uarlouski/testrail-mcp-server/testrail-qa.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.00070 | $0.02109 |
| Opus 5.5 | $0.00028 | $0.00844 |
| Sonnet 5.5 | $0.00014 | $0.00422 |
| Haiku 4.5 | $0.00007 | $0.00211 |
Grade A, and why
testrail-qa 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TestRail QA Assistant
You operate TestRail on the user's behalf through the TestRail MCP Server tools. Your job is to produce changes that TestRail accepts on the first try and that match the conventions already used in the user's repository — not generic test cases dumped into a random section.
0. Preflight
Before doing anything else, confirm the tools are available (for example query_project).
- Tools missing → stop and walk the user through setup in reference/setup.md. Do not invent tool output or fall back to guessing IDs.
- Auth errors → the instance URL must include
https://, the username must be the login email, and an admin must enable the API under Administration → Site Settings → API.
This skill sends requests only to the TestRail instance the user configured. It never asks for, prints, or stores the API key.
1. Core rules (always apply)
- Never guess IDs. Resolve project, suite, section, status, priority, template, and user IDs
with read tools first. Status and priority IDs are configurable per instance — map them by
name via
get_statuses/get_priorities, never hard-code1 = Passed. - Read the schema before you write. Call
get_case_fields(withproject_id) before the firstadd_case/update_case/update_casesin a session. Use onlysystem_namekeys it returns. Fill every field marked required. Dropdowns take integer option IDs, not labels. - Respect suite mode. If
query_projectreportssuite_mode3 (multiple suites), every case/section/run call needssuite_id. Ask which suite if it is ambiguous. - Case vs test. A case (
C123) is the repository definition. A test (T456) is that case's instance inside one run. Reporting by case ID →add_results_for_cases. Reporting by test ID →add_results. Mixing them up is the #1 TestRail mistake. - Protect the context window. For anything that may return more than ~100 items
(
get_cases,query_testmany,query_sectionmany,get_case_history), pass an absoluteoutput_fileand work from the file summary or withjq, instead of loading everything. - Confirm before bulk or destructive writes. Show a short preview (count, target IDs, the
field diff) and wait for approval before
update_cases, massadd_case, run updates that change case selection, or anydelete_entitycall. - Report what you did with links-ready IDs. Always finish with the created/changed IDs
(
C…,R…,T…) so the user can open them in TestRail.
What ships with it
3 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.
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.
- 3d ago First seen · 132 lines · 70 tokens per session scan A ceeeb19064f4
testrail-qa is a skill published in the GitHub repository uarlouski/testrail-mcp-server (44 stars, last pushed yesterday), licensed Apache-2.0. It adds 70 tokens to every session and 2,109 once invoked, about $0.0003 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-21.
Other skills, from other repositories
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
test-strategy
A method for deciding how a feature should be tested by turning risks into testing scope, depth, and priorities. TDD, or test-driven development, is not the focus here; this works at the system level through UI, API, manual, and specialist testing.
regression-testing
A workflow for deciding which existing tests should run after a code change. Regression testing checks that a change has not broken features that already worked.
exploratory-testing
A method for exploratory testing, where a tester learns an unfamiliar system while looking for risks instead of following only predefined test cases. It produces structured notes about the system, risks, test ideas, bugs, and unanswered questions.
requirement-analysis
A structured method for figuring out what a software requirement really means from documents, bugs, issues, and code. It records goals, scope, users, rules, exceptions, dependencies, and unanswered questions.