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/jukrap/ai-agent-playbook/commit-worklog-guardrailsnpx skills add jukrap/ai-agent-playbook --skill commit-worklog-guardrailsgit clone --depth 1 https://github.com/jukrap/ai-agent-playbookWrote 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/jukrap/ai-agent-playbook/commit-worklog-guardrails)<a href="https://agentmods.dev/skills/jukrap/ai-agent-playbook/commit-worklog-guardrails"><img src="https://agentmods.dev/badge/skills/jukrap/ai-agent-playbook/commit-worklog-guardrails.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.00036 | $0.00218 |
| Opus 5 | $0.00018 | $0.00109 |
| Sonnet 5 | $0.00007 | $0.00044 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
commit-worklog-guardrails 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 6d 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
Commit Worklog Guardrails
Primary route: delivery/git-worklog-guardrails.
Protect unrelated changes, local-only files, and verification integrity.
Workflow
- Check branch, remote, upstream, dirty files, and staged files.
- Stage only explicit files related to the task.
- Run project-defined verification and report only commands actually executed.
- Write structured Conventional Commit messages unless the repo proves another convention.
- Suggest a checkpoint commit when a verified logical slice, large diff, many touched files, or mixed concern set would be clearer as a separate commit.
- Push only to the intended remote/branch.
- Write detailed worklogs for milestones, blockers, large direction changes, or long debugging.
Reference
Read references/git-worklog-checklist.md before committing, pushing, writing PR bodies, or creating worklogs.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 25 lines · 36 tokens per session scan A 3a3ec3b77f04
commit-worklog-guardrails is a skill published in the GitHub repository jukrap/ai-agent-playbook (2 stars, last pushed 21d ago), licensed MIT. It adds 36 tokens to every session and 218 once invoked, about $0.0002 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-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
comet-safe-delivery
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下，提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.
conventional-commits
Enforce, validate, lint, and manage Conventional Commits across git repositories. Generates semantic changelogs and installs git hooks. Use this skill whenever the user mentions commit messages, commit conventions, conventional commits, semantic versioning, changelogs, commit linting, git hooks for commits, or wants…
changelog
Use when writing a changelog or release notes. Covers what belongs in one, writing for users rather than for git, semantic versioning, and documenting breaking changes so nobody is surprised.
git-workflow
Use for branching, committing, history repair, and release hygiene. Covers atomic commits, rebase versus merge, bisect, reflog recovery, and undoing mistakes safely.
mx-pr
Draft a pull request from the feature spec and git log, run an autonomous commit-history cleanup (content check), then publish to GitHub, GitLab, or Bitbucket — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].