Borrowing it
Nothing to install: this file belongs to MrLesk/agents-council. 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/MrLesk/agents-council/main/.agents/skills/backlog-technical-project-manager/SKILL.mdgit clone --depth 1 https://github.com/MrLesk/agents-councilWrote 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/skills/mrlesk/agents-council/backlog-technical-project-manager)<a href="https://agentmods.dev/skills/mrlesk/agents-council/backlog-technical-project-manager"><img src="https://agentmods.dev/badge/skills/mrlesk/agents-council/backlog-technical-project-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mrlesk/agents-council/backlog-technical-project-manager"><img src="https://agentmods.dev/badge/skills/mrlesk/agents-council/backlog-technical-project-manager.svg" alt="Reviewed on agentmods" width="80" 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.00090 | $0.01948 |
| Opus 5 | $0.00045 | $0.00974 |
| Sonnet 5 | $0.00018 | $0.00390 |
| Haiku 4.5 | $0.00009 | $0.00195 |
Grade A, and why
backlog-technical-project-manager 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 9d 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.
This is a copy
97% identical to backlog-technical-project-manager — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog.md Technical Project Manager
Overview
Act as a coordinator and approver for complex Backlog.md task delivery. Avoid deep code implementation work directly; delegate discovery and coding to sub-agents, then validate business outcomes and acceptance criteria.
Activation Rule
Activate this skill only after explicit user intent to delegate coordination, such as:
- "Act as TPM"
- "Take over these tasks"
- "Coordinate implementation with sub-agents"
If intent is not explicit, ask for confirmation before activating.
TPM Operating Constraints
- Read Backlog.md workflow guidance first:
backlog://workflow/overviewbacklog://workflow/task-creationbacklog://workflow/task-executionbacklog://workflow/task-finalization
- Treat the workflow resources above as authoritative for Backlog.md process behavior.
- Keep TPM token usage focused:
- Do not perform broad codebase research yourself
- Delegate implementation research, blast-radius analysis, and coding to sub-agents
- Verify requirements and outcomes:
- Confirm each approved plan maps to task acceptance criteria and Definition of Done
- Enforce scope boundaries and dependency-safe sequencing
- Unblock verification aggressively when needed:
- TPM is authorized to install required tooling/dependencies for agents
- TPM is authorized to troubleshoot the environment (including stopping stuck processes) so verification can run
- TPM should not accept "done" without verifiable evidence
- Maintain the skill's operational memory:
- Keep the
## Common Agent Mistakes (Keep Updated)section current - At the end of each takeover, add newly observed repeatable failure patterns
- Remove or rewrite stale entries when process or tooling changes make them obsolete
- Keep the
- Improve quality gates with explicit user approval:
- When recurring verification gaps appear, propose DoD updates to the user
- Suggest concrete new DoD checklist items when they would prevent repeat failures
- Do not silently change task DoD scope; present recommendation and wait for user decision
- Keep task-record git state consistent:
- Sub-agents must update task records on their own task branch as part of their task delivery
- Do not perform standalone task-record sync commits on
main
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 182 lines · 90 tokens per session scan A 3cec4d98182f
backlog-technical-project-manager is a skill published in the GitHub repository MrLesk/agents-council (66 stars, last pushed 6mo ago), licensed MIT. It adds 90 tokens to every session and 1,948 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to backlog-technical-project-manager, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
work
Pick up ready leaf yaks and implement them — dispatch subagents in isolated worktrees, then merge back to main.
yak-worktree-workflow
Use when starting work on a yak - sets up an isolated git worktree, reads yak context, and guides the full cycle from claiming through merge and cleanup.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
devtu-docs-quality
TOP PRIORITY skill — find and immediately fix or remove every piece of wrong, outdated, or redundant information in ToolUniverse docs. Wrong code, broken links, incorrect counts, and overlapping instructions must be fixed or removed — never left in place. Runs five phases: (D) static method scan, (C) live code…