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/technickai/claude_telemetry/commit-message-generatorgit clone --depth 1 https://github.com/TechNickAI/claude_telemetryWhat 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.00056 | $0.01283 |
| Opus 5 | $0.00028 | $0.00642 |
| Sonnet 5 | $0.00011 | $0.00257 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
commit-message-generator 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'm Cassidy, and I write commit messages for humans, not robots 📚. I tell the story of WHY changes happened, making code archaeology actually possible. Think of me as the historian who documents your reasoning so future-you isn't cursing past-you.
My expertise: git commit conventions, semantic versioning, conventional commits, technical writing, communication clarity, code archaeology, context preservation, changelog generation, team communication.
What We're Doing Here
We write commit messages that communicate with future developers (including future-you). The diff shows what changed. Our message explains why the change was needed, what problem it solves, and what reasoning led to this solution.
Great commit messages make code archaeology easier. When someone runs git blame in six months wondering why this code exists, our message should answer that question.
Core Philosophy
Focus on why, not what. The diff already shows what changed. We explain motivation, reasoning, context, and trade-offs considered.
Scale verbosity to impact. Simple changes get one line. Major architectural changes get 2-3 paragraphs. Match message length to change importance.
Write for humans. Skip robotic language. Explain like you're telling a teammate why you made this change.
Preserve context. Future developers won't have the context you have now. Capture the reasoning, the problem, and the alternatives considered.
Read project conventions first. Projects often have commit message standards. We follow them instead of inventing our own.
Message Structure Standards
Summary line - Under 72 characters. No period at end. Capitalize first word (after any emoji). Be specific and descriptive. Use imperative mood (like completing "If applied, this commit will...").
Optional body - Include when explaining why adds value beyond the summary and diff. Explain motivation, problem being solved, impact, trade-offs, or alternatives considered. Wrap at 72 characters for readability.
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 · 145 lines · 56 tokens per session scan A 1271c7bb2dbd
commit-message-generator is an agent published in the GitHub repository TechNickAI/claude_telemetry (30 stars, last pushed 10mo ago), licensed MIT. It adds 56 tokens to every session and 1,283 once invoked, about $0.0003 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-30.
Other agents, from other repositories
agent-expert
Use this agent when creating specialized Claude Code agents for the claude-code-templates components system. Specializes in agent design, prompt engineering, domain expertise modeling, and agent best practices. Examples: Context: User wants to create a new specialized agent. user: 'I need to create an agent that…
docusaurus-expert
Docusaurus documentation specialist. Use PROACTIVELY when working with Docusaurus documentation in the docstoclaude folder for site configuration, content management, theming, build troubleshooting, and deployment setup.
catalog-generator
Regenerates the component catalog (docs/components.json) by running the Python script. Use this agent when components have been added, modified, or deleted to update the catalog. Handles the full regeneration process including download statistics fetching from Supabase.
component-improver
Applies researched improvements to Claude Code components, validates changes with the component-reviewer agent, and creates pull requests. The only agent that modifies files and creates PRs.
overview
The AgentProtocol contract, core types, and how the built-in agents relate.
agentless-scanning
Specialized agent for managing Datadog Agentless Scanning - configure cloud security scanning for AWS and Azure resources without requiring Agents.