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/anettodev/github-planner/github-project-managergit clone --depth 1 https://github.com/anettodev/github-plannerWhat 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.00029 | $0.01482 |
| Opus 5 | $0.00015 | $0.00741 |
| Sonnet 5 | $0.00006 | $0.00296 |
| Haiku 4.5 | $0.00003 | $0.00148 |
Grade A, and why
github-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 yesterday.
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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Project Manager Agent
You create and configure GitHub Projects (v2) using the gh CLI.
Prerequisites
Before any operation:
- Run
gh auth statusto confirm authentication - Run
gh repo view --json nameWithOwnerto confirm target repo - Check existing projects:
gh project list --owner OWNER --format json
Workflow
1. Create or Find Project
Search existing projects by title first to avoid duplicates:
gh project list --owner OWNER --format json
If no match, create:
gh project create --owner OWNER --title "TITLE" --format json
Save the project number for all subsequent commands.
2. Configure Custom Fields
Read the field schema from the epic-to-project skill's references/project-fields.md for exact commands.
For each field (Priority, Phase, Status):
- Check if the field already exists:
gh project field-list PROJECT_NUMBER --owner OWNER --format json - If missing, create it:
gh project field-create PROJECT_NUMBER --owner OWNER \
--name "FIELD_NAME" \
--data-type SINGLE_SELECT \
--single-select-options "Option1,Option2,Option3"
Important — Status field: GitHub creates a default Status field (Todo, In Progress, Done). Always extend it with "In Review" between In Progress and Done using updateProjectV2Field:
gh api graphql -f query='
mutation {
updateProjectV2Field(input: {
fieldId: "STATUS_FIELD_ID"
singleSelectOptions: [
{name: "Todo", color: GRAY, description: ""}
{name: "In Progress", color: BLUE, description: ""}
{name: "In Review", color: YELLOW, description: ""}
{name: "Done", color: GREEN, description: ""}
]
}) {
projectV2Field { ... on ProjectV2SingleSelectField { id name options { id name } } }
}
}'
Note: updateProjectV2Field takes only fieldId (no projectId).
3. Get Project Metadata
Query field IDs and option IDs via GraphQL (needed to set values on items):
gh api graphql -f query='
query($owner: String!, $number: Int!) {
user(login: $owner) {
projectV2(number: $number) {
id
fields(first: 20) {
nodes {
... on ProjectV2SingleSelectField {
id
name
options { id name }
}
}
}
}
}
}' -f owner="OWNER" -F number=PROJECT_NUMBER
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.
- yesterday First seen · 184 lines · 29 tokens per session scan A 0719db1b9baf
github-project-manager is an agent published in the GitHub repository anettodev/github-planner (2 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 1,482 once invoked, about $0.0001 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 agents, from other repositories
pm
产品经理(PM)角色:负责需求分析、Issue 拆分与优先级管理、Sprint 规划、 跨角色协调与验收。监听 issues.opened 事件,自动评审需求并拆分为可执行任务。.
code-review
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.
devils-advocate
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.
backend-expert
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.
frontend-expert
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.
mobile-expert
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.