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 claude-world/director-mode-lite --skill smart-commitgit clone --depth 1 https://github.com/claude-world/director-mode-liteWrote 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/claude-world/director-mode-lite/smart-commit)<a href="https://agentmods.dev/skills/claude-world/director-mode-lite/smart-commit"><img src="https://agentmods.dev/badge/skills/claude-world/director-mode-lite/smart-commit/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/claude-world/director-mode-lite/smart-commit"><img src="https://agentmods.dev/badge/skills/claude-world/director-mode-lite/smart-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.00687 |
| Opus 5.5 | $0.00020 | $0.00275 |
| Sonnet 5.5 | $0.00010 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
smart-commit 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Commit
Create a high-quality commit for current changes.
Execution
- Inventory changes: run
git statusandgit diff(plusgit diff --stagedfor already-staged work) to see everything that changed. - Group related changes into logical commits — list the files that belong to each group so one commit maps to one concern.
- Run available quality gates (test suite, linter, formatter) if the project configures them, and fix failures before committing.
- Stage each group in turn with
git add <files>. - Craft a Conventional Commits message —
type(scope): description, with a body that explains why the change was made. - Commit the staged group.
- Confirm the result with
git log --oneline -n(choosento cover the commits you just made).
Repeat steps 4-6 for each group so unrelated changes land in separate commits. The format and type reference below is your guide for steps 5-6.
Pre-Commit Checklist
Scope Check
- Solves one problem only
- No unrelated changes
- No debug code
- No temporary files
Quality Check
- All tests pass
- Code is formatted
- No linting errors
- Documentation updated
Commit Message Format
<type>(<scope>): <description>
<body>
<footer>
Type (Required)
| Type | Use When |
|---|---|
feat |
New feature (user-visible) |
fix |
Bug fix |
docs |
Documentation only |
test |
Adding/updating tests |
refactor |
Code restructure (no behavior change) |
style |
Formatting (no logic change) |
chore |
Maintenance, dependencies |
perf |
Performance improvement |
Scope (Optional)
Module, component, or file affected:
feat(auth): add login endpointfix(api): handle null responsedocs(readme): update installation steps
Description (Required)
- 50 characters or less
- Present tense, imperative mood
- Lowercase first letter
- No period at end
- Describe WHAT, not HOW
Examples
Feature
feat(user): add email verification
Implement email verification flow for new user registration.
Users must verify email before accessing protected features.
Closes #42
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 · 108 lines · 49 tokens per session scan A 78d06bc809b1
smart-commit is a skill published in the GitHub repository claude-world/director-mode-lite (80 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 687 once invoked, about $0.0002 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 skills, from other repositories
kanso-commit
Use when the user asks to commit changes, stage their work, write commit messages, or split the working tree into logical commits.
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…
claude-code-bash-patterns
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.
catchup
Answer "where did I stop?" for this project. Gives three short groups, done, open and next, taken from the last chat, the recorded to-dos, the last handoff note and git. Use when the user comes back to a project, starts a new chat, or asks where they left off. It writes nothing.