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 FarzamMohammadi/the-engineer --skill commitgit clone --depth 1 https://github.com/FarzamMohammadi/the-engineerWrote 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/farzammohammadi/the-engineer/commit)<a href="https://agentmods.dev/skills/farzammohammadi/the-engineer/commit"><img src="https://agentmods.dev/badge/skills/farzammohammadi/the-engineer/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/farzammohammadi/the-engineer/commit"><img src="https://agentmods.dev/badge/skills/farzammohammadi/the-engineer/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.00028 | $0.00940 |
| Opus 5.5 | $0.00011 | $0.00376 |
| Sonnet 5.5 | $0.00006 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Skill
Analyze code changes, group them into logical packages where appropriate, to create sequential, clear, descriptive commits with effective titles and detailed descriptions.
Levels of Detail
| Level | Component | Purpose |
|---|---|---|
| Highest | Title | Single sentence capturing all changes comprehensively yet succinctly |
| Middle | Description | One level deeper - enough to fully understand without viewing files |
| Lowest | Files | The actual diff - reader can inspect directly if needed |
Step 1: Grouping
Analyze all changes and determine commit packages.
Grouping Priority:
| Priority | Criterion | Example |
|---|---|---|
| 1 | Feature cohesion | All files for user auth feature |
| 2 | Directory scope | All changes in auth/ module |
| 3 | Logical separation | Config changes separate from code |
| 4 | Dependency order | Interface before implementation |
Split Decision:
- Can describe in one sentence? → Single commit
- Multiple unrelated changes? → Split by concern
- Too complex for one sentence? → Split by logical phase
Commit Sequence (when splitting):
- What change enables or defines the others? → Commit first
- Would a reviewer understand each commit in isolation?
- Does the sequence tell a coherent story?
- Order so earlier commits provide context for later ones
Step 2: Title
Write one sentence that:
- Captures ALL changes at the highest level
- Is concise but comprehensive - effective word choice matters
- Clearly conveys what changed without granular file-by-file details
- Capitalize first letter and proper nouns (Claude Code, GitLab, OAuth2, README)
- Imperative mood ("Add" not "Added")
- No period at end
- Max 72 characters (prefer under 50)
Good:
Add OAuth2 authentication to login flowUpdate GitLab MR skill to fetch all commentsRefactor design guide into modular directory structure
Bad:
fix bug(too vague)Updated the thing(past tense, vague)Add feature, fix bug, update docs(multiple things - split it)Add auth system — OAuth2 + JWT + session management(details after dash belong in description, not title)
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 · 135 lines · 28 tokens per session scan A 0cffab5fd368
commit is a skill published in the GitHub repository FarzamMohammadi/the-engineer (12 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 940 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
akigitcommit
Analyze the working tree and commit changes in clean logical groups. Triages a long half-finished tree first (finished vs mid-edit vs abandoned vs accidental) before grouping. Auto-detects CHANGELOG to switch between domain-grouped mode (3–5 commits by object/feature) and type-grouped mode (feat/fix/refactor). Stages…
ship-change
Ship an OpenSpec change after openspec-apply completes. When only QA/manual tasks remain, marks them done (tested later), archives + syncs specs, commits, pushes, opens a PR against develop, watches CI, waits for CodeRabbit, auto-applies safe fixes and re-pushes, loops until CI green + no actionable review threads…
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…