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/aakashg/pm-github-workflow-repo/claude-mdgit clone --depth 1 https://github.com/aakashg/pm-github-workflow-repoWrote 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/aakashg/pm-github-workflow-repo/claude-md)<a href="https://agentmods.dev/instructions/aakashg/pm-github-workflow-repo/claude-md"><img src="https://agentmods.dev/badge/instructions/aakashg/pm-github-workflow-repo/claude-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.00380 | $0.00380 |
| Opus 5 | $0.00190 | $0.00190 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
pm-github-workflow-repo CLAUDE.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.
What it actually says
CLAUDE.md
Who I Am
- Role: [YOUR ROLE]
- Company: [YOUR COMPANY]
- Product: [YOUR PRODUCT]
- Team: [X] engineers, [X] designers
How I Work
- I prototype before I spec.
- I write PLANNING.md in the project repo.
- I commit skill changes only after testing on 3+ inputs.
Voice
- Direct. No filler. No "I'd be happy to help."
- PRDs: hypothesis first, then metrics with thresholds.
- Data analysis: show the method. Reproducibility matters.
Current Focus
- [PROJECT 1]: [one line]
- [PROJECT 2]: [one line]
Rules
- Never commit to GitHub without asking me first.
- Never modify files in evals/ without confirming the change and reason.
- Check skills/ folder when I reference a skill by name.
- Responses under 500 words unless I ask for depth.
Tools
- Skills: see skills/ folder
- MCPs: [YOUR MCPS]
- CLIs: GitHub CLI, [OTHERS]
Keep this file under 200 lines. Monthly, review what changed and prune: git log -p -- CLAUDE.md (or git diff HEAD~20 -- CLAUDE.md once you have 20+ commits - it errors on younger repos).
Project-specific context goes in project-level CLAUDE.md files, not here (the calendar PR rule that briefly lived here is the example - see the prune commit).
On-demand instructions go in skill files, not here.
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 · 40 lines · 380 tokens per session scan A 679bedabfdc4
pm-github-workflow-repo CLAUDE.md is an instructions file published in the GitHub repository aakashg/pm-github-workflow-repo (2 stars, last pushed 3mo ago), licensed MIT. It adds 380 tokens to every session, about $0.0019 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).