Borrowing it
Nothing to install: this file belongs to julianoczkowski/product-manager. 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/julianoczkowski/product-manager/main/AGENTS.mdgit clone --depth 1 https://github.com/julianoczkowski/product-managerWrote 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/julianoczkowski/product-manager/agents-md)<a href="https://agentmods.dev/instructions/julianoczkowski/product-manager/agents-md"><img src="https://agentmods.dev/badge/instructions/julianoczkowski/product-manager/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.01037 | $0.01037 |
| Opus 5 | $0.00518 | $0.00518 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
product-manager 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- product-manager CLAUDE.md — 89% identical, 16 lines differ
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for working on this repo. This is the Product Manager Copilot plugin — a Codex / Codex Desktop plugin that packages product-management Agent Skills built on the Pragmatic Institute Framework.
Repo layout
.Codex-plugin/plugin.json— plugin manifest. Noversionfield on purpose (see Releasing below).displayNameisProduct Manager Copilot; pluginnameisproduct-manager..Codex-plugin/marketplace.json— marketplace manifest (product-manager-marketplace).skills/<name>/SKILL.md— one folder per skill. Skills are auto-discovered from this folder; the manifests do not enumerate them.skills/pm-copilot/references/— shared knowledge base (framework.md,journey.md,artifact-output.md). The router and stage skills read these.README.md,CHANGELOG.md— keep both current when behavior changes.
Skill conventions
- Every skill name is prefixed
pm-(pm-copilot,pm-personas,pm-positioning, …) so typing/pm-surfaces the whole toolkit and avoids collisions with generically named skills from other plugins. When adding a skill, prefix itpm-. - Folder name must equal the
name:field in that skill'sSKILL.mdfrontmatter. - Cross-references between skills use backticked names (e.g.
`pm-personas`). The router's routing tables live inreferences/journey.mdandreferences/framework.md— update them when adding, removing, or renaming a skill. - Auto-activation is driven by the
description:field, not the name. Keep descriptions specific and intent-rich.
How updates reach installed users (IMPORTANT)
Installed clients do not see changes just because they were pushed to main. The
Codex Desktop marketplace tracks a synced commit and only advances it when the user
acts:
- Each install shows "Synced commit: " with two controls: "Check for updates"
(pulls the latest commit on
main) and a "Sync automatically" toggle (off by default). - The fix when a user reports stale skills: have them click "Check for updates" (or enable "Sync automatically"). This — not a new release tag — is what actually advances an installed Desktop plugin to the latest commit.
- The Codex CLI equivalent is
/plugin marketplace update product-manager-marketplacethen/reload-plugins; force-refresh by deleting~/.Codex/plugins/cache/product-manager-marketplace/product-manager/and reloading.
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.
- 7d ago First seen · 80 lines · 1,037 tokens per session scan A 3af4ff78c55a
product-manager AGENTS.md is an instructions file published in the GitHub repository julianoczkowski/product-manager (31 stars, last pushed 1mo ago), licensed MIT. It adds 1,037 tokens to every session, about $0.0052 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.