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/sprngr/rubber-duck/agents-mdgit clone --depth 1 https://github.com/sprngr/rubber-duckWrote 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/sprngr/rubber-duck/agents-md)<a href="https://agentmods.dev/instructions/sprngr/rubber-duck/agents-md"><img src="https://agentmods.dev/badge/instructions/sprngr/rubber-duck/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.01513 | $0.01513 |
| Opus 5 | $0.00757 | $0.00757 |
| Sonnet 5 | $0.00303 | $0.00303 |
| Haiku 4.5 | $0.00151 | $0.00151 |
Grade A, and why
rubber-duck 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 5d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
What this is
Rubber Duck is a Socratic AI assistant project. It focuses on decision quality, evidence-first reasoning, and bounded safe changes.
This repository contains source prompts, assembled skills, generated harness artifacts, installers, validation fixtures, and policy docs.
Quick Start (5 minutes)
- Verify tools:
bash,pwsh,python3,node/npx,jq,make - Build generated artifacts:
make build
- Verify generated artifacts are clean:
make check
- Run validation suite:
make validation
- Install locally (example):
- Bash:
./scripts/rubber-duck.sh install --opencode - PowerShell:
./scripts/rubber-duck.ps1 install -OpenCode
- Bash:
Layout
src/- source-of-truth for agents, skills, and shared snippetssrc/install/scripts/- sync wrapper templatessrc/install/templates/- manifest template
skills/- built skill artifacts generated fromsrc/skills/*dist/- built harness artifacts generated fromsrc/agents/*dist/scripts/- generated sync wrapper scriptsdist/templates/- generated manifest template
scripts/- build, check, and installer scripts (rubber-duck.sh,rubber-duck.ps1)docs/- architecture and supporting documentationvalidation/- prompt validation suite, fixtures, and runnertests/- fixture-style behavior tests and expected outputs.github/- tracked CI/workflow config.agents/,.claude/,.opencode/- local harness install targets (untracked, populated by installers)build/- assembly/check rules
Tooling and Runtimes
- Bash (Linux/macOS/CI script runtime)
- PowerShell (
pwsh) for Windows installer runtime - Python 3 (validation runner and build checks)
- Node.js +
npx(skills CLI install/remove/list flows) jq(required for harness artifact build rendering)make(task entrypoints for build/check workflows)
Commands & Scripts
- Build everything:
make build
- Verify generated artifacts + guardrails drift:
make check
- Build/check skills only:
make build-skillsmake check-skills
- Build/check harness artifacts only:
make build-harnessmake check-harness
- Run validation suite:
make validation- or
python3 validation/run-validation-tests.py
- Installers:
- Bash:
./scripts/rubber-duck.sh install --opencode - PowerShell:
./scripts/rubber-duck.ps1 install -OpenCode
- Bash:
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.
- 5d ago First seen · 156 lines · 1,513 tokens per session scan A a5e36795042d
rubber-duck AGENTS.md is an instructions file published in the GitHub repository sprngr/rubber-duck (8 stars, last pushed yesterday), licensed MIT. It adds 1,513 tokens to every session, about $0.0076 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-31.
Other instructions, from other repositories
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).
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.
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.
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).