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 FerroxLabs/ijfw --skill ijfw-commitgit clone --depth 1 https://github.com/FerroxLabs/ijfwWrote 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/ferroxlabs/ijfw/ijfw-commit)<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-commit"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-commit.svg" alt="Measured on agentmods" 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.00022 | $0.00285 |
| Opus 5 | $0.00011 | $0.00143 |
| Sonnet 5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
ijfw-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 yesterday.
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
Write commit messages following Conventional Commits.
Format: type(scope): subject
Rules:
- Subject ≤50 chars. Imperative mood.
- Why over what. The diff shows what changed.
- Types: feat, fix, refactor, docs, test, chore, perf, ci, style
- Scope: affected module/component (optional but preferred)
- Body only if the "why" isn't obvious from the subject.
- No "Updated", "Changed", "Modified" -- be specific.
Examples:
- fix(auth): prevent token refresh race condition
- feat(api): add rate limiting to public endpoints
- refactor(db): extract connection pool into service
After commit completes successfully, run in the same shell:
command -v ijfw >/dev/null 2>&1 && ijfw cross critique HEAD~1..HEAD &
Then narrate to the user using this exact structure:
- One line:
Phase N / Wave NA -- Step N.M -- commit -- done. - One line: SHA + subject (e.g.
a1b2c3d feat(api): add rate limiting) - One line:
Background critique running -- check /ijfw-status for findings.(omit if ijfw not present)
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.
- yesterday First seen · 31 lines · 22 tokens per session scan A 1f99839fd17b
ijfw-commit is a skill published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 6d ago), licensed MIT. It adds 22 tokens to every session and 285 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-09-05.
Other skills, from other repositories
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
pr-package
Prepare a clean delivery package for GitHub from the real git diff vs an explicit base branch, persisted as PRPACKAGE.md (or PRPACKAGE. .md for multi-repo tasks). Produces branch name, commit messages, fetch, checkout, add, commit, and push commands, PR title and body, and reviewer attention points; never invents work…
branch-commit
Return a branch name and a concise commit message (at most 2 lines) for the current task, grounded in the real git diff rather than a paraphrase of the task summary, and with --apply optionally create that commit after showing it and getting the user's confirmation in the same turn. Use when the user only needs quick…
task-workspace
Provision, report, or attach a dedicated git worktree and branch for the active task on a git-backed project, so multiple tasks run in parallel on one repository without colliding on a single working tree. Opt-in and git-gated: a non-git project or an un-opted task is a no-op. Records the worktree path and task branch…
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…