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/bguivarch/skillforgeWrote 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/commands/bguivarch/skillforge/commit)<a href="https://agentmods.dev/commands/bguivarch/skillforge/commit"><img src="https://agentmods.dev/badge/commands/bguivarch/skillforge/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/commands/bguivarch/skillforge/commit"><img src="https://agentmods.dev/badge/commands/bguivarch/skillforge/commit.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.00000 | $0.00923 |
| Opus 5.5 | $0.00000 | $0.00369 |
| Sonnet 5.5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Commit
Analyze Git changes and generate a conventional commit message following the Commitizen format.
Arguments
$ARGUMENTS- Optional: Additional context or instructions for the commit message
Instructions
Generate a conventional commit message by analyzing the current Git changes.
Step 1: Gather Git Information
Run these commands in parallel:
git status- See staged and unstaged changesgit diff --cached- See staged changes (what will be committed)git diff- See unstaged changesgit log --oneline -5- See recent commit style for consistency
Step 2: Analyze the Changes
Based on the diff, determine:
-
Type - Choose the most appropriate type:
feat— A new featurefix— A bug fixdocs— Documentation only changesstyle— Formatting, white-space, missing semi-colons (no code change)refactor— Code change that neither fixes a bug nor adds a featureperf— Performance improvementtest— Adding or correcting testsbuild— Changes to build system or dependenciesci— Changes to CI configurationchore— Other changes (tooling, config, etc.)revert— Reverts a previous commit
-
Scope — The area of the codebase affected (optional but recommended):
- Use lowercase, kebab-case
- Examples:
task,auth,api,db,channel,note - Derive from folder structure or feature name
-
Description — A short, imperative summary:
- Use imperative mood ("add" not "added" or "adds")
- Don't capitalize first letter
- No period at the end
- Max 50 characters
-
Breaking Change — If this introduces breaking changes:
- Add an exclamation mark after the scope:
feat(api)!: remove deprecated endpoint - Or add a footer:
BREAKING CHANGE: explanation here
- Add an exclamation mark after the scope:
Step 3: Format the Commit Message
Follow the Conventional Commits specification:
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
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 · 128 lines · 0 tokens per session scan A 8a697e7d6ecb
commit is a command published in the GitHub repository bguivarch/skillforge (3 stars, last pushed 8mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 923 tokens. 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 commands, from other repositories
checkpoint
Full memory flush — refresh state.md, append to activity log, route any new decisions/insights, then commit and push.
git-commit
IMPORTANT: This command ONLY runs when explicitly invoked via /git-commit. Do NOT auto-commit after code modifications. Wait for user to explicitly run /git-commit.
git-push
IMPORTANT: This command ONLY runs when explicitly invoked via /git-push. Do NOT auto-push after commits or modifications. Wait for user to explicitly run /push.
ci-guard
Trigger the Commit & Branch Guard workflow on demand.
commit-push-pr
A command that creates a Git commit, sends it to a remote repository, and opens a pull request. A pull request is a request for others to review and merge code changes.
commit
A commit command from a Claude plugin marketplace, with a description referring to background information and instructions.