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/businesslens/pdd/agents-mdgit clone --depth 1 https://github.com/businesslens/pddWrote 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/businesslens/pdd/agents-md)<a href="https://agentmods.dev/instructions/businesslens/pdd/agents-md"><img src="https://agentmods.dev/badge/instructions/businesslens/pdd/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.02162 | $0.02162 |
| Opus 5 | $0.01081 | $0.01081 |
| Sonnet 5 | $0.00432 | $0.00432 |
| Haiku 4.5 | $0.00216 | $0.00216 |
Grade A, and why
pdd 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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidance
Purpose
This repository is the BusinessLens OSS core: the businesslens npm package
plus the agent skills that build and maintain the .businesslens/ product
map.
Two engineering contracts, each changed before the behavior it governs:
spec/format.md— the authored.businesslens/folder. Change it before changing the parser or the linter.spec/report.md— the Product Report wire contract, its portable projection, and expansion. Change it before changingexport,open,pull,contribute, or anything the catalog server agrees with.
Neither is a docs-site page. The user-facing explanation of the same entities
lives in the Product Model group under docs/, and the two registers must not
contradict each other.
Layout
src/cli.ts— public command dispatch:install,update,lint,view, and theblueprintnamespace (export,open,pull,contribute). Bare spellings andbuildare refused with a message naming the replacement — no aliases, so a name can be reused later without changing meaning underneath anyone.src/commands/— public command implementations.src/core/providers.ts— supported harness paths and detection.src/core/skill-installation.ts— ownership-safe skill installation.src/core/— parsers, model loading, Git context, portable schema, and catalog/contribution support.layers/nuxt/report-viewer/— the stable Nuxt Product Report, its complete report projection, and its dependency-free topology engine.layers/nuxt/report-viewer-lab/— the private, unexported extension point for temporary Product Report experiments used only by the local viewer.layers/nuxt/theme/— the separately extendable BusinessLens-wide visual foundation and approved identity used across Nuxt hosts, not only report pages.layers/nuxt/theme-lab/— the optional shared experiment layer for backgrounds and their audition controls.viewer/app/— the private static Nuxt host bundled into the CLI forbusinesslens view.skills/businesslens-*/SKILL.md— one independent skill per workflow:businesslens-map,businesslens-ideate, andbusinesslens-verify.test/fixtures/fixture-shop/— the golden lint fixture.
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 · 166 lines · 2,162 tokens per session scan A c33acd36f659
pdd AGENTS.md is an instructions file published in the GitHub repository businesslens/pdd (10 stars, last pushed yesterday), licensed MIT. It adds 2,162 tokens to every session, about $0.0108 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
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.