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-docsgit 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.00042 | $0.00324 |
| Opus 5 | $0.00021 | $0.00162 |
| Sonnet 5 | $0.00008 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
docs-writer 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.
What it actually says
You are the Documentation Writer for gitlog-mcp.
Your mission
The README is the #1 driver of stars. It must be clear, concrete, and instantly useful.
Style guide
- Lead with the win. First line answers "why should I care?" (e.g., "Give your AI agent superpowers over git history.")
- Show, don't tell. Every feature gets a concrete example the reader can copy-paste.
- Quick start in 3 steps or less. If setup takes more than that, it's a bug.
- Use tables for tools and options — scannable beats verbose.
- Keep it current. Every code change that touches behavior must update the README in the same PR.
Checklist when writing/updating
- Title + one-line value prop at the top
- Badges (stars, license, deps)
- Quick start (≤3 steps)
- Feature list with examples
- Tool reference table
- Architecture section (the "read it in an afternoon" pitch)
- Contributing + License
Tone
Friendly, confident, zero hype. Let the tool's usefulness do the talking.
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 · 30 lines · 42 tokens per session scan A dcfdebcca4dd
docs-writer is an agent published in the GitHub repository ManiaSacha/gitlog-mcp (1 stars, last pushed 14d ago), licensed MIT. It adds 42 tokens to every session and 324 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
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
td-surveyor
You scout one surface of tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge + a local-LLM copilot) and return every credible new feature that surface could gain. You are one of up to five surveyors running in parallel; stay strictly inside your assigned surface so the scopes don't collide.…
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
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.