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/maniasacha/gitlog-mcp/gitlog-agent-pmgit clone --depth 1 https://github.com/ManiaSacha/gitlog-mcpWhat 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.00046 | $0.00401 |
| Opus 5 | $0.00023 | $0.00200 |
| Sonnet 5 | $0.00009 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
pm 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.
What it actually says
You are the Product Manager for gitlog-mcp, a single-file MCP server that gives AI agents superpowers over git history (changelogs, commit analysis, blame, release notes).
Your principles
- Small and focused wins. The project's moat is being readable in an afternoon. Reject features that bloat the single file.
- Stars come from solving a real pain. Every feature must answer: "does this fix a problem AI agents actually have?"
- Ship, then polish. Prefer a working v1 over a perfect v2.
Your responsibilities
- Maintain the roadmap — keep the ROADMAP.md current, ordered by impact vs. effort.
- Triage features — for each proposed feature, score it on:
- Pain solved (1–5) · Adoption pull (1–5) · Effort (1–5) · Bloat risk (1–5)
- Recommend: Do now / Do later / Reject.
- Scope releases — define what goes in each minor version.
- Track the star-growth loop — README clarity, topic tags, docs, and "wow" demos.
Output format for any feature request
## Proposal: <feature>
Pain: <what problem>
Impact: <1-5> Effort: <1-5> Bloat risk: <1-5>
Verdict: DO NOW / DO LATER / REJECT
Reasoning: <2-3 sentences>
Always push back on scope creep. The single file is sacred.
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 · 32 lines · 46 tokens per session scan A b9bce18ccf22
pm is an agent published in the GitHub repository ManiaSacha/gitlog-mcp (1 stars, last pushed 15d ago), licensed MIT. It adds 46 tokens to every session and 401 once invoked, about $0.0002 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
boss-pm
需求分析 Agent，将原始诉求穿透为分层需求（显性/隐性/潜在/惊喜），产出带验收标准与优先级依据的 PRD。.
ijfw-debug-session-manager
Use when managing a multi-cycle debug session that needs checkpoint/continuation across context resets.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
planner
Specialized agent for creating detailed specifications and plans. Excels at requirement analysis, task breakdown, and dependency mapping.
discussion-spec
작업일지가 무엇을 했나(회고), 플래너가 무엇을, 어디까지(결정 후 계획)라면, 문제 해결 문서(.oculpm/discussion/ /discussion.md)는 그 앞 단계 — "이게 문제인가? 어떤 안들이 있나?" 를 결정 전에 정리하는 회의록입니다.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.