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 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-courseWrote 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/decodingai-magazine/building-a-coding-agent-from-scratch-course/commit)<a href="https://agentmods.dev/skills/decodingai-magazine/building-a-coding-agent-from-scratch-course/commit"><img src="https://agentmods.dev/badge/skills/decodingai-magazine/building-a-coding-agent-from-scratch-course/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/decodingai-magazine/building-a-coding-agent-from-scratch-course/commit"><img src="https://agentmods.dev/badge/skills/decodingai-magazine/building-a-coding-agent-from-scratch-course/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.00016 | $0.00267 |
| Opus 5.5 | $0.00006 | $0.00107 |
| Sonnet 5.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 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.
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.
- 1mo 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 (664 stars, last pushed 7d ago), licensed Apache-2.0. It adds 16 tokens to every session and 267 once invoked, about $0.0001 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
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
cuga-contributor-workflows
Run CUGA contributor workflows: Conventional Commits, create pull requests against origin with gh and PR templates, and ruff check/format via uv. Use when the user says commit, create a commit, create PR, pull request, open a PR, ruff check, ruff format, or conventional commits.
push-all
Use when the user explicitly asks to stage all current changes, create a commit, and push to the remote after safety checks.
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…
ship-it
A GitHub delivery workflow that commits completed changes, pushes a branch, creates and merges a pull request, and closes the related issue.
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.