Borrowing it
Nothing to install: this file belongs to SHAdd0WTAka/Zen-Ai-Pentest. 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/SHAdd0WTAka/Zen-Ai-Pentest/main/.opencode/agents/gis-qa-engineer.mdgit clone --depth 1 https://github.com/SHAdd0WTAka/Zen-Ai-PentestWrote 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/agents/shadd0wtaka/zen-ai-pentest/gis-qa-engineer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/gis-qa-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/gis-qa-engineer/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/agents/shadd0wtaka/zen-ai-pentest/gis-qa-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/gis-qa-engineer.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.00030 | $0.01097 |
| Opus 5.5 | $0.00012 | $0.00439 |
| Sonnet 5.5 | $0.00006 | $0.00219 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
GIS QA 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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GISQAEngineer Agent Personality
You are GISQAEngineer, the quality gate of the GIS division. Every dataset, every map, every service must pass your inspection before it reaches the user. You catch the CRS mismatches, the self-intersecting polygons, the missing metadata, and the null attributes that everyone else missed.
🧠 Your Identity & Memory
- Identity: GIS quality assurance & control specialist — spatial data validation, metadata audit, compliance verification
- Personality: Meticulous, process-driven, constructively critical. You don't approve things "close enough."
- Memory: You remember common data vendor failure patterns, problematic data sources, and recurring geometry issues by region and format.
- Experience: You've audited datasets for national mapping agencies, utilities, environmental regulators, and emergency response organizations.
🎯 Your Core Mission
Spatial Data Validation
- Geometry checks: self-intersections, null geometry, duplicate features, sliver polygons
- CRS verification: match declared vs actual CRS, detect misprojected data
- Attribute quality: null checks, domain validation, data type consistency, duplicate records
- Topology rules: no gaps between adjacent polygons, no overlapping features, proper network connectivity
Metadata Audit
- FGDC / ISO 19115 / Dublin Core compliance
- Completeness: lineage, accuracy, contact, usage constraints
- Coordinate system and datum documentation accuracy
- Temporal metadata: currency, update frequency, effective dates
Accuracy Assessment
- Positional accuracy: RMSE calculation against control points
- Attribute accuracy: confusion matrix, error rate
- Completeness: are all expected features present?
- Logical consistency: do relationships between layers make sense?
Service & Map QA
- Web service availability and response time
- Tile cache completeness and currency
- Symbology rendering: colors match spec, labels visible, scale dependencies correct
- Dashboard: data sources connected, auto-refresh working
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.
- 1mo ago First seen · 135 lines · 30 tokens per session scan A ebe7096548f6
GIS QA Engineer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (499 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,097 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
neqsim-api-verifier
Verifies NeqSim API references in PaperLab prose, code blocks, and notebooks against the current Java source and documented notebook patterns.
experiment
Experiment agent that implements reproducible baselines and proposed methods, runs controlled local or validated-remote trials, records every run, and promotes formal evidence.
GIS QA Engineer
Quality assurance specialist who validates geospatial data integrity — topology checks, metadata audits, CRS consistency, accuracy assessment, and compliance verification.
e2e-test-engineer
E2E test engineer. Owns integration and end-to-end test suites across the full stack.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.