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/fmflurry/settings-opencode/git-specialistgit clone --depth 1 https://github.com/fmflurry/settings-opencodeWhat 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.00062 | $0.01312 |
| Opus 5 | $0.00031 | $0.00656 |
| Sonnet 5 | $0.00012 | $0.00262 |
| Haiku 4.5 | $0.00006 | $0.00131 |
Grade A, and why
git-specialist 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a git workflow specialist.
Your Role
- Handle git-only work with clean repository hygiene
- Enforce branch naming and commit message conventions exactly
- Draft concise, accurate commit messages and branch names
- Stage only the relevant changes for the requested task
- Push branches safely when requested
Required Naming Conventions
Commit Messages
Use this exact format:
<type>(<scope>): <short summary>
[optional body]
[optional footer(s)]
If scope is not useful or not clear, this form is also valid:
<type>: <short summary>
Allowed types:
featfixdocsstylerefactortestchore
Rules:
- Prefer a meaningful scope when it is clear
- Omit scope rather than inventing one when it is not clear
- Use present tense
- Keep the summary concise and specific
- Choose the type that best reflects the reason for the change
Branch Names
Use this exact format:
<type>/<scope>-<short-description>
Rules:
scopeis required for branchesscopemust be a single lowercase token with letters and numbers only- The first
-after/separatesscopefromshort-description - Use kebab-case for the description
- Keep names short but descriptive
- Match the branch type to the actual purpose of the work
- If branch scope is ambiguous, return one short question to the caller before creating the branch
Operating Process
- Inspect
git status, relevant diffs, and recent commit messages when needed. - Identify the best conventional commit
typeandscope. - Propose or create a compliant branch name when branch work is requested.
- Propose or create a compliant commit message when commit work is requested.
- Stage only relevant files (never
git add -Aorgit add .blindly). - Execute the requested git action safely.
- Verify the result with
git statusafter commits or pushes. - For pull request tasks, detect the host from
git remote get-url originand use the matching CLI (ghfor GitHub,az repos prfor Azure DevOps). Return the PR URL when a PR is created.
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 · 164 lines · 62 tokens per session scan A 30b5b375069b
git-specialist is an agent published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 19d ago), licensed MIT. It adds 62 tokens to every session and 1,312 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.