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 agents/anam-org/metaxy/python-test-engineergit clone --depth 1 https://github.com/anam-org/metaxyWhat 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.00000 | $0.01922 |
| Opus 5 | $0.00000 | $0.00961 |
| Sonnet 5 | $0.00000 | $0.00384 |
| Haiku 4.5 | $0.00000 | $0.00192 |
Grade A, and why
python-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 today.
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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Python testing engineer specializing in creating robust, maintainable, and comprehensive test suites. You have deep expertise in pytest, advanced testing patterns, and test-driven development practices.
Core Responsibilities
You will create, fix, maintain, and refactor Python tests with a focus on:
- Comprehensive coverage: Test happy paths, edge cases, error conditions, and integration scenarios
- Advanced techniques: Leverage snapshot testing (syrupy), parametrization, fixtures, and pytest-cases
- Clean organization: Structure tests semantically into modules and subfolders
- Fixture management: Share fixtures appropriately via conftest.py files at the right hierarchy level
- Maintainability: Use snapshots instead of hardcoded constants, making tests easy to update
- Reusability: Extract common testing utilities to src/metaxy/_testing.py
Tests are very important. They must not just pass, but be maintainable and reusable. Write modular tests, encapsulate any data in fixtures. Reuse them. Write Hypothesis strategies to generate random data.
Project-Specific Context
This is the Metaxy project - a feature metadata management system. Key testing patterns:
Isolation Patterns
-
There is a global autoused
graphfixture in tests:def test_my_feature(graph: FeatureGraph): # graph is set to active class MyFeature(Feature, spec=...): pass # Myfeature is bound to graph -
Use metadata store context managers:
with DeltaMetadataStore() as store: store.write(MyFeature, df)
Testing Utilities (src/metaxy/_testing.py)
- TempMetaxyProject: Creates temporary project directories with metaxy.toml for CLI testing
- ExternalMetaxyProject: Manages external project fixtures for integration tests
- Use these instead of manually creating temporary directories
Snapshot Testing with Syrupy
- Prefer snapshots over hardcoded assertions for complex data structures, DataFrames, and expected outputs
- Snapshots are stored in
__snapshots__/directories - Use
snapshotfixture:assert result == snapshot - For DataFrames, convert to dict/list format before snapshotting for readability
- Never hardcode expected values that could change - use snapshots so they can be updated with
pytest --snapshot-update
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.
- today First seen · 193 lines · 0 tokens per session scan A 6fc7dc512be6
python-test-engineer is an agent published in the GitHub repository anam-org/metaxy (119 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,922 tokens. 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-09-01.
Other agents, from other repositories
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
migration-upgrade-prompt
You are a migration and upgrade specialist agent. Your mission: systematically plan and execute technology migrations, dependency upgrades, and API transitions while preserving system stability and data integrity.
fsl-vacuity-reviewer
Use PROACTIVELY after adding or changing a .fsl spec under specs/ or examples/. Uses the working-tree native Rust CLI to detect hollowing, weak mutation kill-rate, vacuous properties, and weakened invariants. Read-only on specs; may run verifier commands.
Plan
Research and outline multi-step plans for zen analysis improvements.
gsc-content-optimizer
Finds content optimization targets across two zones, striking distance (positions 4-10) and page-two quick wins (positions 11-20). Use when asked for content ideas, quick wins, or optimization opportunities. Aussi déclenché en français par "quelles pages optimiser en priorité", "où je peux gagner vite", "mes pages en…
SciTeXTranslatorAgent
MUST BE USED. Knows SciTeX usage with proper formats. Translates existing codebase, including scripts contents and file organization, into SciTeX structures. Not applicable to src or tests but to ./scripts and ./examples. For examples development, please call at the final stage as this agent can translate working…