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 instructions/deitum/testops-mcp/agents-mdgit clone --depth 1 https://github.com/deitum/testops-mcpWhat 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 | $0.02139 | $0.02139 |
| Opus 5 | $0.01069 | $0.01069 |
| Sonnet 5 | $0.00428 | $0.00428 |
| Haiku 4.5 | $0.00214 | $0.00214 |
Grade A, and why
testops-mcp AGENTS.md 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guide
Guidance for developers and coding agents changing a clone of this repository. It is not runtime documentation: the MCP server never reads or exposes this file, and no end-user workflow may depend on it. Commands and house style live in CONTRIBUTING.md; what follows is the contract that must survive a change.
Product Contract
This repository is @deitum/testops-mcp, a stdio MCP server for Allure TestOps. An MCP client
spawns dist/cli.js, which exposes tools for test cases, Markdown import, launches and statistics.
The server is deliberately single-project:
TESTOPS_PROJECT_IDis required and is the only source of the target project.- Never expose
projectIdin an MCP input schema or in a caller-controlled request type. TestOpsClientmust inject its configured project into every project-scoped API request. Caller data must not be able to override it.- Before a public by-ID read or mutation whose endpoint is not reliably project-scoped, load the
entity and fail closed unless its returned
projectIdmatches the configured project. Internal post-create import writes may use the freshly created ID without another lookup. - Working with another project means changing the environment value and restarting the server.
Markdown import is a single MCP operation with a complete preflight. testcase_import_markdown must
parse and validate the whole file, load the configured project's custom-field catalog, resolve
human-readable field and value names, and stop before creating the first case if preflight has
errors. Structurally invalid files must be rejected before the catalog request. After preflight,
writes are sequential and non-transactional: the result statuses are completed, refused,
failed and outcome_unknown, and the report distinguishes created, partiallyCreated,
failedCase and notAttempted. Never perform an import retry, deletion or rollback automatically.
Do not reintroduce legacy mode/dryRun, caller-supplied projectId, custom-field IDs in
Markdown, or a mandatory separate catalog call.
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 · 150 lines · 2,139 tokens per session scan A 0f65bbee8e97
testops-mcp AGENTS.md is an instructions file published in the GitHub repository deitum/testops-mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 2,139 tokens to every session, about $0.0107 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-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.