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/benseverndev-oss/goldenpipe/agents-mdgit clone --depth 1 https://github.com/benseverndev-oss/goldenpipeWrote 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/benseverndev-oss/goldenpipe/agents-md)<a href="https://agentmods.dev/instructions/benseverndev-oss/goldenpipe/agents-md"><img src="https://agentmods.dev/badge/instructions/benseverndev-oss/goldenpipe/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.1 | $0.01839 | $0.01839 |
| Opus 5 | $0.00920 | $0.00920 |
| Sonnet 5 | $0.00368 | $0.00368 |
| Haiku 4.5 | $0.00184 | $0.00184 |
Grade A, and why
goldenpipe 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 4d 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.
This is a copy
100% identical to goldenpipe copilot-instructions.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoldenPipe
Golden Suite orchestrator -- chains GoldenCheck, GoldenFlow, GoldenMatch.
Related Projects
- GoldenCheck:
D:\show_case\goldencheck-- Data validation. Has its own CLAUDE.md. - GoldenFlow:
D:\show_case\goldenflow-- Data transformation. Has its own CLAUDE.md. - GoldenMatch:
D:\show_case\goldenmatch-- Entity resolution. Has its own CLAUDE.md. - GitHub:
benzsevern/goldenpipe,benzsevern/goldencheck,benzsevern/goldenflow,benzsevern/goldenmatch
Branch & Merge SOP (all Golden Suite repos)
- Feature work goes on
feature/<name>branches, never directly to main - Merge via squash merge PR (watchers see PR activity, history stays clean)
- PR title format:
feat: <description>orfix: <description> - Merge when: tests pass, docs updated. Days not weeks.
- After merge: delete remote branch
Environment
- Windows 11, bash shell (Git Bash)
- Python 3.12 at
C:\Users\bsevern\AppData\Local\Programs\Python\Python312\python.exe - Two GitHub accounts:
benzsevern(personal) andbenzsevern-mjh(work) - MUST
gh auth switch --user benzsevernbefore push, switch back tobenzsevern-mjhafter
Architecture
goldenpipe/pipeline.py-- Pipeline class, run() function. ONLY file that imports from tools.goldenpipe/decisions.py-- Adaptive logic (decide_flow, decide_match). NO tool imports. Testable independently.goldenpipe/cli/main.py-- Typer CLI- Tools imported with try/except ImportError guards (HAS_CHECK, HAS_FLOW, HAS_MATCH)
- Data flows as Polars DataFrames in memory between stages
Pipeline Flow
load_file -> GoldenCheck.scan_file(path) -> decide_flow(findings)
-> if fixable: GoldenFlow.transform_df(df) -> updated df
-> decide_match(findings, row_count, strategy_override)
-> GoldenMatch.dedupe_df(df) or AgentSession.deduplicate(path)
-> PipeResult
Testing
pytest --tb=shortfrom project root- test_decisions.py: no tool deps, tests pure decision logic
- test_pipeline.py: requires goldencheck, goldenflow, goldenmatch installed
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.
- 4d ago First seen · 178 lines · 1,839 tokens per session scan A e274ae0c79e1
goldenpipe AGENTS.md is an instructions file published in the GitHub repository benseverndev-oss/goldenpipe (0 stars, last pushed 4mo ago), licensed MIT. It adds 1,839 tokens to every session, about $0.0092 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to goldenpipe copilot-instructions.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
goldenflow copilot-instructions.md
Copilot instructions for benseverndev-oss/goldenflow, covering goldenflow, related projects, branch & merge sop (all golden suite repos), environment and commands.
goldenflow AGENTS.md
AGENTS.md instructions for benseverndev-oss/goldenflow, covering goldenflow, related projects, branch & merge sop (all golden suite repos), environment and commands.
goldenmatch AGENTS.md
AGENTS.md instructions for benseverndev-oss/goldenmatch, covering golden suite monorepo — agent guide, what this is, layout, build & test and landmines to know before you touch anything.
goldenmatch CLAUDE.md
Claude Code instructions for benseverndev-oss/goldenmatch, covering golden suite monorepo, typescript: pnpm + turborepo (post-2026-05-02 fold), ci (.github/workflows/ci.yml), ci path filters (post-2026-05-06, pr #89) and merge queue: main serializes merges fifo (since 2026-06-15).
databricks-template CLAUDE.md
Instructions for andre-salvati/databricks-template, covering claude.md, project overview, tooling: mcp servers, cli, skills → see specs/tooling.md, commands and architecture & data model → see specs/.
James-RAG-Evol CLAUDE.md
Claude Code instructions for Hashevolution/James-RAG-Evol, covering sekos / james — session briefing for claude code, what james is, where we are right now, critical rules for this session and where to look next.