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/dtannen/pm/agents-mdgit clone --depth 1 https://github.com/dtannen/pmWhat 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.01453 | $0.01453 |
| Opus 5 | $0.00727 | $0.00727 |
| Sonnet 5 | $0.00291 | $0.00291 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
pm 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 2d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents integrating with this repository. It explains what this repo is, how to interact with it via MCP tools, and how to apply the Response Awareness (RA) methodology while working.
What This Repo Is
This project is a Python-based project/epic/task manager with a real-time dashboard and an MCP (Model Context Protocol) server so agents can collaborate programmatically.
- Name: project-manager-mcp
- Backend: FastAPI + WebSockets (MCP + updates)
- DB: SQLite (WAL), schema for projects → epics → tasks (+ task logs)
- CLI:
project-manager-mcppluspython -m task_manager.cli - Dashboard: single-page UI served by the backend
- MCP Tools: create/update/list tasks, acquire/release locks, RA tagging, etc.
See README.md for installation, usage, and architecture details.
MCP: How Agents Integrate
The server exposes a set of MCP tools that agents call to query, plan, execute, and verify work. Common tools include:
get_available_tasks: Find work by status, exclude locked tasksacquire_task_lock: Atomically lock a task (moves status to IN_PROGRESS)update_task_status: Single-call status change with auto-lockingrelease_task_lock: Explicitly release a held lockcreate_task/update_task: CRUD with full RA metadata supportget_task_details: Full task + logs + dependencieslist_projects/list_epics/list_tasks: Hierarchical queriesadd_ra_tag: Create RA tags with automatic context capture
Transport modes:
stdio(default): for local/CLI integrationsse: HTTP SSE endpoint for network clients
Refer to README.md and docs/ for details and examples.
Start With A Task (Required)
Before you do any work, you must create or select a task to work on.
- Why: Ensures ownership, locking, logging, RA tags, and status tracking.
- How:
- MCP:
create_taskwithname,description, andepic_id/project_id(optionally setra_mode/ra_score). - Dashboard: Create a task via the UI in the correct project/epic.
- Scope: If your work spans multiple concerns, split into separate tasks.
- MCP:
- Then: Acquire a lock (
acquire_task_lock) before making changes, or rely on single-callupdate_task_statusfor short operations (auto-locking).
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.
- 2d ago First seen · 144 lines · 1,453 tokens per session scan A 3ce2f12b12eb
pm AGENTS.md is an instructions file published in the GitHub repository dtannen/pm (0 stars, last pushed 10mo ago), licensed MIT. It adds 1,453 tokens to every session, about $0.0073 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.