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 monkilabs/opencastle --skill git-workflowgit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/git-workflow)<a href="https://agentmods.dev/skills/monkilabs/opencastle/git-workflow"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/git-workflow/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/monkilabs/opencastle/git-workflow"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/git-workflow.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.00036 | $0.00417 |
| Opus 5.5 | $0.00014 | $0.00167 |
| Sonnet 5.5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
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 10d 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
Git Workflow
Never push to main. Every change goes through a branch and a pull request, and a person merges it.
| Branch | From main: <type>/<slug>, or <type>/<issue-id>-<slug> when there is an issue. Types: feat, fix, refactor, perf, docs, chore |
| Commits | Small and atomic, with an imperative subject — the issue ID first when there is one (TAS-42: Fix token refresh) |
| History | Never --force or --amend on a shared branch; --force-with-lease on your own only |
| Secrets | None in commits, pull request bodies or output; a leaked one is rotated at once |
Deliver
-
Commit, then push:
git push -u origin <branch>. -
Open the pull request with its body in a file — an inline
--bodybreaks on backticks and quotes in zsh:cat > /tmp/pr-body.md << 'EOF' Resolves TAS-42 ## Changes - ... EOF GH_PAGER=cat gh pr create --base main --title "TAS-42: Short description" --body-file /tmp/pr-body.md -
Do not merge it. Link it from the tracker issue when there is one.
The tracker
When the project uses one, its conventions are in .opencastle/project/<tracker>-config.md and the skill bound to the task-management slot. Without its tools in this session, list the issues you would have created — title and acceptance criteria — in your answer, and carry on.
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.
- 10d ago Changed · -16 lines · +5 tokens per session ff8a19724095
- 12d ago Changed · -7 tokens per session 23556c8f0aac
- 19d ago Changed 7e6e3eac22ba
- 1mo ago First seen · 53 lines · 38 tokens per session scan A 26023ec52915
git-workflow is a skill published in the GitHub repository monkilabs/opencastle (80 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 417 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
gentle-ai-work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
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.
github
A general GitHub skill for understanding repositories, pull requests, and issues through a connected GitHub account. It helps route work to more specific GitHub workflows when needed.
git-analysis
Answer questions from repository history, including what changed, when, by whom, why a line exists, which commits touched an area, where a regression entered, and how branches relate. Use for blame, bisect-style narrowing, changelog drafting, and release diffs.
github
Create issues, PRs, and query repositories.
gh-address-comments
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.