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 skills add majiayu000/claude-skill-registry --skill ac-commit-managergit clone --depth 1 https://github.com/majiayu000/claude-skill-registryWrote 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/skills/majiayu000/claude-skill-registry/ac-commit-manager)<a href="https://agentmods.dev/skills/majiayu000/claude-skill-registry/ac-commit-manager"><img src="https://agentmods.dev/badge/skills/majiayu000/claude-skill-registry/ac-commit-manager/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/skills/majiayu000/claude-skill-registry/ac-commit-manager"><img src="https://agentmods.dev/badge/skills/majiayu000/claude-skill-registry/ac-commit-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 113 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00031 | $0.00696 |
| Opus 5 | $0.00015 | $0.00348 |
| Sonnet 5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
ac-commit-manager 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 9d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AC Commit Manager
Manage git commits for completed feature implementations.
Purpose
Creates well-structured git commits after each feature completion, ensuring proper version control and clear project history.
Quick Start
from scripts.commit_manager import CommitManager
manager = CommitManager(project_dir)
result = await manager.commit_feature("auth-001")
Commit Workflow
1. VALIDATE → Ensure changes are safe to commit
2. STAGE → Stage relevant files
3. MESSAGE → Generate descriptive commit message
4. COMMIT → Create the commit
5. VERIFY → Verify commit was created
6. TAG → Optional: tag milestone commits
Commit Message Format
feat(auth): implement user registration (#auth-001)
- Add registration endpoint with email/password
- Implement password hashing with bcrypt
- Add input validation for email format
- Create user model and database migration
Test: All 5 acceptance criteria passing
Coverage: 92%
Feature: auth-001
Status: passes
Commit Result
{
"success": true,
"commit_hash": "abc123def456",
"feature_id": "auth-001",
"message": "feat(auth): implement user registration",
"files_changed": [
"src/auth/register.py",
"src/models/user.py",
"tests/test_auth_001.py"
],
"stats": {
"insertions": 145,
"deletions": 12,
"files_changed": 3
}
}
Commit Categories
Based on feature category:
feat: New featuresfix: Bug fixesrefactor: Code refactoringtest: Test additions/changesdocs: Documentationchore: Maintenance tasksperf: Performance improvements
Pre-Commit Checks
# Run validation before commit
validation = await manager.pre_commit_check()
if validation.can_commit:
await manager.commit_feature(feature_id)
Checks include:
- No uncommitted sensitive files
- All tests pass
- Linting passes
- No merge conflicts
Atomic Commits
Each feature gets exactly one commit:
- Includes implementation + tests
- Self-contained and revertable
- Descriptive message with context
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 137 lines · 31 tokens per session scan A 84a27c632d1f
ac-commit-manager is a skill published in the GitHub repository majiayu000/claude-skill-registry (598 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 696 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-30.
Other skills, from other repositories
git-commit
Run git commit using Angular conventional commit format. Use when the user asks to commit, create a commit, /git-commit, or save changes to git. Also trigger on "snapshot this", "save my work", "check in changes", "wrap up", "ship this locally", or whenever the user finishes a logical unit of work and the tree is…
iso-commit
Write a commit message and commit. Conventional Commits subject (type(scope): message), body is a plain dot list of what the work does — only when the subject doesn't already cover it. No Co-Authored-By, no AI attribution, no LLM filler. Stages everything by default; --staged commits the index only. Use when invoked…
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
manuscript-as-code
Treat manuscripts as software: version control, reproducible builds, figure pipelines, CI, and structured repo layout. Helps teams avoid 'finalv7' chaos and ensures submission-ready artifacts.