Borrowing it
Nothing to install: this file belongs to Rekin226/aquascope. 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/Rekin226/aquascope/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/Rekin226/aquascopeWrote 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/instructions/rekin226/aquascope/copilot-instructions)<a href="https://agentmods.dev/instructions/rekin226/aquascope/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/rekin226/aquascope/copilot-instructions.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.00919 | $0.00919 |
| Opus 5 | $0.00460 | $0.00460 |
| Sonnet 5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
aquascope copilot-instructions.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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for AquaScope
AquaScope is a water data aggregation toolkit with AI-powered research methodology recommendations. It collects water-quality and hydrology data from 8 global sources, normalises them into unified Pydantic schemas, and uses an AI engine to recommend and auto-execute research methodologies.
Build, Test, and Lint
# Install with all optional dependencies (ML, viz, LLM, dev tools)
pip install -e ".[dev,all]"
# Run all tests
pytest
# Run a single test file
pytest tests/test_collectors/test_taiwan_moenv.py
# Run a single test by name
pytest -k "test_normalise_produces_correct_records"
# Lint
ruff check aquascope/ tests/
# Type check
mypy aquascope/ --ignore-missing-imports
CI runs lint and type-check on Python 3.12; tests on 3.10, 3.11, and 3.12.
Architecture
The data flow is a pipeline:
Collectors (fetch + normalise) → Pydantic Schemas → Analysis (EDA, Quality) → AI Recommender → Pipelines (execute)
collectors/— 8 source modules, each subclassingBaseCollector. Implementfetch_raw()andnormalise()to return unified schema objects.schemas/water_data.py— Pydantic models (WaterQualitySample,WaterLevelReading,ReservoirStatus,SDG6Indicator) plus aDataSourceenum.analysis/—eda.pyfor dataset profiling,quality.pyfor assessment and preprocessing.ai_engine/—knowledge_base.pydefines 26ResearchMethodologyentries;recommender.pyscores them against aDatasetProfile(rule-based + optional LLM).pipelines/model_builder.py— 7 executable pipeline functions registered in_PIPELINE_REGISTRY, each returning aPipelineResult.utils/—http_client.py(CachedHTTPClient with retries and rate limiting),storage.py(save to JSON/CSV).cli.py— 7 argparse commands:collect,recommend,eda,quality,run,list-methods,list-sources. Uses lazy imports — modules are imported inside command functions.
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.
- 8d ago First seen · 68 lines · 919 tokens per session scan A 19e60d7647bb
aquascope copilot-instructions.md is an instructions file published in the GitHub repository Rekin226/aquascope (25 stars, last pushed today), licensed MIT. It adds 919 tokens to every session, about $0.0046 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.