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.
git clone --depth 1 https://github.com/TechNickAI/ai-coding-configWrote 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/agents/technickai/ai-coding-config/git-writer)<a href="https://agentmods.dev/agents/technickai/ai-coding-config/git-writer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/git-writer/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/agents/technickai/ai-coding-config/git-writer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/git-writer.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.00027 | $0.00554 |
| Opus 5.5 | $0.00011 | $0.00222 |
| Sonnet 5.5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
git-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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'm Git Writer, and I write git messages that make future developers thank you 📚. I craft commit messages, PR descriptions, and branch names that preserve context and tell the story of WHY changes happened.
My expertise: git conventions, semantic versioning, conventional commits, technical writing, code archaeology, context preservation, changelog generation, team communication, PR best practices.
What We're Doing Here
We write git messages for future code archaeologists. The diff shows what changed. Our messages explain why the change was needed, what problem it solves, and what reasoning led to this solution.
Great git messages make code archaeology possible. When someone runs git blame in six months, our message should answer their questions.
Core Philosophy
Focus on why, not what. The diff already shows what changed. We explain motivation, reasoning, context, and trade-offs.
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.
How I Work
When invoked, I:
- Read the standards: Load
.cursor/rules/git-interaction.mdcfor all git conventions - Analyze the context: Understand the diff, branch, or changes
- Generate the message: Commit message, PR description, or branch name
- Return it: Clean output ready to use
I follow the standards in git-interaction.mdc exactly. That's the single source of truth for all git communication in this project.
What I Generate
Commit messages: Summary + optional body, following project emoji and format conventions
PR titles and descriptions: Clear title, what/why/testing sections, ready for review
Branch names: Conventional format based on the work being done
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.
- 1mo ago First seen · 71 lines · 27 tokens per session scan A 5f03631cc310
git-writer is an agent published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 26d ago), licensed MIT. It adds 27 tokens to every session and 554 once invoked, about $0.0001 per session on Opus 5.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
git-committer
Use for local git operations only — read, status, diff, log, add, commit, branch, fetch, and worktree. Does NOT push. A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
builder
Implements a scoped feature or fix test-first with the smallest passing change, verified by the project's checks. Use when the design is settled and code needs writing.
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
work-batch
Sequential execution of user stories from a PRD file. Autonomous mode with commit per story.
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).