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 instructions/transferwise/pipelinewise/agents-mdgit clone --depth 1 https://github.com/transferwise/pipelinewiseWrote 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/transferwise/pipelinewise/agents-md)<a href="https://agentmods.dev/instructions/transferwise/pipelinewise/agents-md"><img src="https://agentmods.dev/badge/instructions/transferwise/pipelinewise/agents-md.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 | $0.01317 | $0.01317 |
| Opus 5 | $0.00659 | $0.00659 |
| Sonnet 5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
pipelinewise AGENTS.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 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Coding Agent Instructions
Scope
PipelineWise is a Python 3.12 Singer ELT framework. Write for senior engineers; prioritize operational precision, edge cases, and rationale. Read each relevant guide:
pipelinewise/AGENTS.md: orchestration, FastSync, backend migrations, data-diff.singer-connectors/AGENTS.md: vendored taps and targets.tests/AGENTS.md: unit tests and suite boundaries.tests/end_to_end/AGENTS.md: databases, connectors, E2E,dev-project/.docs/AGENTS.md: documentation.
Scoped guidance adds to this file; explicit user instructions win. Each
CLAUDE.md symlinks to its adjacent AGENTS.md; edit the latter and preserve
the link.
Architecture
- Singer JSON flows as
tap | [transform-field] | [mbuffer] | target; YAML becomes generated config, state, and catalog JSON. pipelinewise/cli/__init__.pydefines argparse and dispatches toPipelineWise. Canonicalfast_syncandimport_configretain deprecated aliasessync_tablesandimport.- FastSync is a native full/filtered bulk-transfer optimization, not a replication method. Singer handles INCREMENTAL/LOG_BASED and FULL_TABLE streams not selected for FastSync.
Environment
- Prefer the
dev-projectDocker stack; its Linux runtime best matches production. Use the host only to manage Docker or when a check cannot run in the container, and report the compatibility gap. - The repo is mounted at
/opt/pipelinewisein thepipelinewisecontainer.PIPELINEWISE_HOMEenvironments live underdev-project/.virtualenvs/and are onPATH. make pipelinewiseinstalls the editable root plus test extras. Connector runtimes use.virtualenvs/<name>/; connector Makefiles may usevenv/. Never mix host, container, root, runtime-connector, or connector-test interpreters, and never use repository.venv/.
Validation
For implementation changes, run these root gates verbatim and in order, preferably in the ready container:
ruff check pipelinewise tests
pylint pipelinewise tests
flake8 pipelinewise --count --select=E9,F63,F7,F82 --show-source --statistics
flake8 pipelinewise --count --max-complexity=15 --max-line-length=120 --statistics
pytest --cov=pipelinewise --cov-fail-under=77 -v tests/units
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 Changed · +4 lines · +60 tokens per session d5eba2a15c00
- 4d ago First seen · 116 lines · 1,257 tokens per session scan A a540af119b3f
pipelinewise AGENTS.md is an instructions file published in the GitHub repository transferwise/pipelinewise (659 stars, last pushed today), licensed Apache-2.0. It adds 1,317 tokens to every session, about $0.0066 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.