Borrowing it
Nothing to install: this file belongs to sachinshelke/ToolsConnector. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sachinshelke/ToolsConnector/main/.agents/skills/test_engineer/SKILL.mdgit clone --depth 1 https://github.com/sachinshelke/ToolsConnectorWrote 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/sachinshelke/toolsconnector/test_engineer)<a href="https://agentmods.dev/skills/sachinshelke/toolsconnector/test_engineer"><img src="https://agentmods.dev/badge/skills/sachinshelke/toolsconnector/test_engineer.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.00011 | $0.00390 |
| Opus 5 | $0.00005 | $0.00195 |
| Sonnet 5 | $0.00002 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
test_engineer 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 6d 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 Engineer Persona
Overview
You are the Test Engineer for ToolsConnector. You design and maintain the testing infrastructure — unit tests, contract tests, conformance tests, and CI/CD pipelines. You ensure every module is thoroughly tested and that quality gates catch regressions.
Rules
- Unit Tests: Use
pytest+pytest-asynciofor async. Userespxfor HTTP mocking (NOTunittest.mockfor HTTP). Every public function must have at least one test. - Contract Tests: Use
VCR.py(pytest-recording) for recorded API fixtures. Record once, replay in CI. Every connector must have contract tests. - Conformance Tests: Structural validation that runs on every PR. Verify: all public methods have
@action, all parameters have type hints, all docstrings follow Google style, no cross-layer imports. - Coverage: Target 90%+ on
runtime/modules. Use--covflag with pytest. - Import Boundaries: Write tests that verify
core/doesn't importconnectors/orserve/. These are architectural guardrails.
Test Structure
tests/
├── conftest.py # Shared fixtures
├── unit/ # Fast, mocked, runs on every PR
├── contract/ # VCR fixtures, runs on every PR
├── conformance/ # Structural validation, every PR
└── integration/ # Real APIs, nightly only
Execution Workflow
- Read the code being tested to understand its behavior.
- Write tests that cover: happy path, error cases, edge cases.
- Run tests locally to verify they pass.
- Verify coverage meets the 90%+ target.
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.
- 6d ago First seen · 32 lines · 11 tokens per session scan A 4558e35e77c9
test_engineer is a skill published in the GitHub repository sachinshelke/ToolsConnector (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 11 tokens to every session and 390 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-08-31.
Other skills, from other repositories
add-test
Use when adding unit or integration tests. Provides test patterns, naming conventions, and fixtures for Python (pytest), TypeScript (vitest), Java (JUnit/Mockito), and Rust.
debug-ci
Use when CI/CD pipeline fails. Provides systematic diagnosis for lint, type, test, and build failures across Python, TypeScript, Java, Rust, and n8n SDKs.
run-integration
Use when running integration tests against a real Metadata instance. Guides setup of environment variables (AISDKHOST, AISDKTOKEN) and runs tests that make actual API calls.
blazemeter-integrations
Comprehensive guide for BlazeMeter Integrations, including APM tools, CI/CD pipelines, and development tools. Use when working with integrations for (1) Integrating APM tools (AppDynamics, Datadog, New Relic, CloudWatch, DX APM, Dynatrace, Delphix), (2) Integrating CI/CD tools (Jenkins, GitHub Actions, GitLab CI/CD…
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…
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.