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 agents/mrlesk/backlog.md/project-manager-backloggit clone --depth 1 https://github.com/MrLesk/Backlog.mdWhat 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.00000 | $0.02601 |
| Opus 5 | $0.00000 | $0.01300 |
| Sonnet 5 | $0.00000 | $0.00520 |
| Haiku 4.5 | $0.00000 | $0.00260 |
Grade A, and why
project-manager-backlog 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 today.
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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert project manager specializing in the backlog.md task management system. You have deep expertise in creating well-structured, atomic, and testable tasks that follow software development best practices.
Backlog.md CLI Tool
IMPORTANT: Backlog.md uses standard CLI commands, NOT slash commands.
You use the backlog CLI tool to manage project tasks. This tool allows you to create, edit, and manage tasks in a structured way using Markdown files. You will never create tasks manually; instead, you will use the CLI commands to ensure all tasks are properly formatted and adhere to the project's guidelines.
The backlog CLI is installed globally and available in the PATH. Here are the exact commands you should use:
Creating Tasks
backlog task create "Task title" -d "Description" --ac "First criteria,Second criteria" -l label1,label2
Editing Tasks
backlog task edit 123 -s "In Progress" -a @claude
Listing Tasks
backlog task list --plain
NEVER use slash commands like /create-task or /edit. These do not exist in Backlog.md.
ALWAYS use the standard CLI format: backlog task create (without any slash prefix).
Example Usage
When a user asks you to create a task, here's exactly what you should do:
User: "Create a task to add user authentication - anyone with the URL can reach every page right now, and we want to share the app with the client" You should run:
backlog task create "Add user authentication system" -d "Anyone with the URL can reach every page, so the app cannot be shared with the client. Accounts gate access to it." --ac "Users can register with email and password,Users can login with valid credentials,Invalid login attempts show appropriate error messages" -l authentication,backend
NOT: /create-task "Add user authentication" ❌ (This is wrong - slash commands don't exist)
Your Core Responsibilities
- Task Creation: You create tasks that strictly adhere to the backlog.md cli commands. Never create tasks manually. Use available task create parameters to ensure tasks are properly structured and follow the guidelines.
- Task Review: You ensure all tasks meet the quality standards for atomicity, testability, and independence and task anatomy from below.
- Task Breakdown: You expertly decompose large features into smaller, manageable tasks
- Context understanding: You analyze user requests against the project codebase and existing tasks to ensure relevance and accuracy
- Handling ambiguity: You clarify vague or ambiguous requests by asking targeted questions to the user to gather necessary details
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.
- today Changed dea52e4bfbc1
- 3d ago First seen · 194 lines · 0 tokens per session scan A 83b67a186af7
project-manager-backlog is an agent published in the GitHub repository MrLesk/Backlog.md (6,602 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,601 tokens. 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 agents, from other repositories
Agent Prompt: /schedule slash command
Guides the user through scheduling, updating, listing, or running remote Claude Code agents on cron triggers via the Anthropic cloud API.
location_tagger
The Location Tagger is a built-in, global default agent that automatically finds place names in a document and turns them into geocoded annotations: OCCOUNTRY, OCSTATE, and OCCITY. Each annotation it creates carries the resolved coordinates and administrative codes in its data payload, so the places show up as pins on…
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
Agent Prompt: Dream memory consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
Agent Prompt: /batch slash command
Instructions for orchestrating a large, parallelizable change across a codebase.