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 skills/decodingai-magazine/building-a-coding-agent-from-scratch-course/commitnpx skills add decodingai-magazine/building-a-coding-agent-from-scratch-course --skill commitgit clone --depth 1 https://github.com/decodingai-magazine/building-a-coding-agent-from-scratch-courseWhat 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.00016 | $0.00267 |
| Opus 5 | $0.00008 | $0.00133 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00027 |
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 2d 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.
What it actually says
You commit the work in the current working tree autonomously: you stage the right files, write
the message, and run git commit. You commit exactly what you stage.
- Inspect the tree with
git statusandgit diff(andgit diff --cachedfor anything already staged). If there is nothing to commit, say so and stop. - Stage the changes that belong in this commit with
git add. Do not stage unrelated edits, build artifacts, or secrets; if the tree mixes unrelated changes, stage the coherent subset and say what you left out. - Compose a Conventional Commits message:
- Subject
type(scope): summary—type∈ feat, fix, refactor, docs, test, chore, build, ci, perf; imperative summary ≤ 72 chars. - A blank line, then a body explaining why the change was made and any notable trade-offs.
- Subject
- Run
git commitwith that message, committing exactly what you staged. Describe only changes you actually saw in the diff; never invent them. Report the resulting commit subject.
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.
- 2d ago First seen · 19 lines · 16 tokens per session scan A e3ee944032a8
commit is a skill published in the GitHub repository decodingai-magazine/building-a-coding-agent-from-scratch-course (338 stars, last pushed 4d ago), licensed Apache-2.0. It adds 16 tokens to every session and 267 once invoked, about $0.0001 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-smart
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
git-commits-and-prs
Load BEFORE creating a git commit or a GitHub pull request. Step-by-step protocol for drafting commit messages, staging safely, amend rules, and gh pr create choreography.
commit
A commit candidate is the exact patch that will enter the commit. A coherent change has one task or issue as its reason for existing.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
git-workflow
Defines branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, task tracking conventions. Load when committing, pushing, or opening PRs.