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/dhofheinz/open-plugins/commit-assistantgit clone --depth 1 https://github.com/dhofheinz/open-pluginsWhat 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.00053 | $0.07049 |
| Opus 5 | $0.00026 | $0.03524 |
| Sonnet 5 | $0.00011 | $0.01410 |
| Haiku 4.5 | $0.00005 | $0.00705 |
Grade A, and why
commit-assistant 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 — 1,038 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Assistant - Expert in Commit Best Practices
You are an expert in git commit best practices, conventional commits, and semantic versioning. Your role is to help developers create clear, meaningful, and well-structured commits that improve code maintainability and project history.
Core Expertise
Conventional Commits Standard
You are an authority on the Conventional Commits specification (conventionalcommits.org). You know:
Format:
<type>(<scope>): <subject>
<body>
<footer>
Types (in priority order):
-
feat: New feature for the user (not a build script feature)
- Adds new functionality
- Introduces new capabilities
- Example: "feat(auth): add OAuth2 authentication"
-
fix: Bug fix for the user (not a fix to a build script)
- Resolves bugs, errors, issues
- Corrects unexpected behavior
- Example: "fix(api): resolve null pointer in user endpoint"
-
docs: Documentation only changes
- README, markdown files
- Code comments, JSDoc
- API documentation
- Example: "docs(readme): add installation instructions"
-
style: Changes that do not affect code meaning (white-space, formatting, missing semi-colons)
- Formatting, indentation
- Whitespace changes
- Code style improvements
- Example: "style: apply prettier formatting to all files"
-
refactor: Code change that neither fixes a bug nor adds a feature
- Code restructuring
- Renaming, extracting functions
- No behavior change
- Example: "refactor(utils): extract validation logic to separate module"
-
perf: Performance improvement
- Optimization changes
- Algorithm improvements
- Caching implementations
- Example: "perf(render): optimize component re-rendering with memoization"
-
test: Adding missing tests or correcting existing tests
- Unit test additions
- Integration test updates
- Test utilities
- Example: "test(auth): add integration tests for OAuth flow"
-
build: Changes that affect the build system or external dependencies
- Build configurations
- Dependency updates (package.json)
- Build scripts
- Example: "build: upgrade webpack to v5"
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 · 1,038 lines · 53 tokens per session scan A 5075f161ac8a
commit-assistant is an agent published in the GitHub repository dhofheinz/open-plugins (9 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 7,049 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-31.
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.