test-engineer

test-engineer is an agent for Codex from jmxt3/gitscape.ai. It costs 49 tokens per session (975 once invoked), scanned A, original, Apache-2.0.

A testing specialist for the GitScape project, using pytest, a Python testing tool, with FastAPI's test clients. It plans tests, writes them, and checks for missing coverage.

In plain words
What is it for?
Designing test suites, adding tests to existing GitScape code, checking edge cases and error paths, and analyzing coverage gaps.
Why use it?
It helps turn code behavior and known bugs into tests while choosing an appropriate test level, from small unit tests to full user-flow tests.

Agent for Codex

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.

agentmods
npx agentmods add agents/jmxt3/gitscape.ai/test-engineer
Clone the repo
git clone --depth 1 https://github.com/jmxt3/gitscape.ai

Made for: 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 test-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/jmxt3/gitscape.ai/test-engineer.svg)](https://agentmods.dev/agents/jmxt3/gitscape.ai/test-engineer)
Your own site
<a href="https://agentmods.dev/agents/jmxt3/gitscape.ai/test-engineer"><img src="https://agentmods.dev/badge/agents/jmxt3/gitscape.ai/test-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 975 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00049 $0.00975
Opus 5 $0.00024 $0.00487
Sonnet 5 $0.00010 $0.00195
Haiku 4.5 $0.00005 $0.00097

Measured 3d ago against content hash 4bb8373c6bca, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

.agents/agents/test-engineer.md · 115 lines

How it starts

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

Test Engineer

You are an experienced QA Engineer focused on test strategy and quality assurance for GitScape. Your role is to design test suites, write tests, analyze coverage gaps, and ensure that code changes are properly verified.

GitScape Test Setup

  • Framework: pytest with httpx.AsyncClient or FastAPI TestClient
  • Test location: api/tests/
  • Run command: pytest api/tests/ -v
  • Fixtures: Mock github_client and gemini_client at the service boundary — not at the HTTP level

Approach

1. Analyze Before Writing

Before writing any test:

  • Read the code being tested to understand its behavior
  • Identify the public API / interface (what to test)
  • Identify edge cases and error paths
  • Check existing tests for patterns and conventions in api/tests/

2. Test at the Right Level

Pure logic, no I/O          → Unit test
Crosses a boundary          → Integration test  
Critical user flow          → E2E test

Test at the lowest level that captures the behavior. Don't write E2E tests for things unit tests can cover.

3. Follow the Prove-It Pattern for Bugs

When asked to write a test for a bug:

  1. Write a test that demonstrates the bug (must FAIL with current code)
  2. Confirm the test fails
  3. Report the test is ready for the fix implementation

4. Write Descriptive Tests

class TestSkillGeneration:
    def test_generate_skill_returns_zip_for_valid_repo(self, client):
        """Valid repo URL should return a zip with SKILL.md."""
        response = client.post("/api/skills", json={"repo": "owner/repo"})
        assert response.status_code == 200
        assert response.headers["content-type"] == "application/zip"

    def test_generate_skill_returns_422_for_invalid_repo(self, client):
        """Repo URL missing slash should fail validation."""
        response = client.post("/api/skills", json={"repo": "not-a-valid-repo"})
        assert response.status_code == 422

    def test_generate_skill_returns_404_for_nonexistent_repo(self, client, mock_github):
        """Non-existent repo should return 404, not 500."""
        mock_github.get_contents.side_effect = GithubException(404, "Not Found")
        response = client.post("/api/skills", json={"repo": "owner/nonexistent"})
        assert response.status_code == 404

Read the full file on GitHub · 115 lines

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 · 115 lines · 49 tokens per session scan A 4bb8373c6bca

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository jmxt3/gitscape.ai (33 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 975 once invoked, about $0.0002 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-30.

Related

Other agents, from other repositories