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/0xnyk/oneclaw/git-workflownpx skills add 0xNyk/oneclaw --skill git-workflowgit clone --depth 1 https://github.com/0xNyk/oneclawWhat 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.00000 | $0.03882 |
| Opus 5 | $0.00000 | $0.01941 |
| Sonnet 5 | $0.00000 | $0.00776 |
| Haiku 4.5 | $0.00000 | $0.00388 |
Grade A, and why
git-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 627 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
When the user asks you to perform git operations, create branches, open PRs, manage releases, or resolve conflicts, follow this guide. These are the procedural patterns you should apply consistently.
Conventional Commits
Every commit message must follow the Conventional Commits specification. This is non-negotiable for all repositories that use this skill.
Format
<type>(<scope>): <subject>
[optional body]
[optional footer(s)]
Types
| Type | When to use |
|---|---|
feat |
A new feature or capability visible to users |
fix |
A bug fix |
docs |
Documentation changes only (README, comments, guides) |
style |
Formatting, whitespace, semicolons -- no logic changes |
refactor |
Code restructuring that does not change external behavior |
perf |
Performance improvement with no functional change |
test |
Adding or updating tests only |
build |
Build system or dependency changes (Cargo.toml, package.json, Dockerfile) |
ci |
CI/CD configuration changes (GitHub Actions, GitLab CI, etc.) |
chore |
Maintenance tasks that do not fit other categories |
revert |
Reverting a previous commit |
Scope
The scope is optional but recommended. Use the module or area of the codebase affected:
feat(memory): add FTS5 hybrid search
fix(gateway): handle empty body in webhook
docs(README): update installation instructions
refactor(providers): extract retry logic into ReliableProvider
Subject line rules
- Use imperative mood: "add feature" not "added feature" or "adds feature"
- Do not capitalize the first letter after the colon
- No period at the end
- Maximum 72 characters for the full first line
- Be specific: "fix auth token refresh" not "fix bug"
Body
Use the body when the subject line alone does not explain the "why":
fix(security): reject tokens with future-dated issuance
Tokens with `iat` claims set in the future were being accepted due to
clock skew tolerance being applied in the wrong direction. This could
allow replay attacks with pre-generated tokens.
Closes #1423
What ships with it
1 file 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.
- 2d ago First seen · 627 lines · 0 tokens per session scan A c4d56d1105b4
git-workflow is a skill published in the GitHub repository 0xNyk/oneclaw (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,882 tokens. 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
electron-pro
Expert in building cross-platform desktop applications using web technologies (HTML/CSS/JS) with the Electron framework.
lat-md
Writing and maintaining lat.md documentation files — structured markdown that describes a project's architecture, design decisions, and test specs. Use when creating, editing, or reviewing files in the lat.md/ directory.
local-tools
Access local system resources including Calendar on macOS and Windows. Use this skill when you need to manage user's schedule directly on their device.
seedance
Generate AI videos using Volcengine Seedance model. Supports text-to-video (T2V), image-to-video (I2V), and audio-synced video generation. Use this skill when the user wants to create or generate videos.
seedream
Generate AI images using Volcengine Seedream model. Supports text-to-image (T2I), image editing (I2I), multi-image fusion, and web-search-based generation. Use this skill when the user wants to create, generate, or edit images.
technology-search
Search tech blogs, developer forums, and IT media (TechCrunch, Hacker News, 36氪, etc.) for software and hardware industry updates with heat ranking and EN↔CN translation. Use this skill only when the topic is clearly about programming, software, hardware, AI, or IT infrastructure.