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/sabbour/agentweaver/agentweaver-git-workflownpx skills add sabbour/agentweaver --skill agentweaver-git-workflowgit clone --depth 1 https://github.com/sabbour/agentweaverWhat 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.00024 | $0.01431 |
| Opus 5 | $0.00012 | $0.00715 |
| Sonnet 5 | $0.00005 | $0.00286 |
| Haiku 4.5 | $0.00002 | $0.00143 |
Grade A, and why
agentweaver-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 3d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Workflow
dev is the default protected integration branch. Use a short-lived issue branch and a
PR targeting dev; PRs are squash-merged so dev has one commit per logical change.
main is stable/published-only and accepts only soaked release promotions or audited
emergency hotfixes.
Issue branches use:
squad/{issue-number}-{kebab-case-slug}
Mandatory Worktree Isolation
Every locally run background agent making code changes MUST work in its own dedicated Git worktree. This is unconditional: it applies to issue-linked work and ad-hoc work alike. Never let a local agent make code changes from the shared primary checkout.
Use these naming conventions:
| Work type | Branch | Worktree |
|---|---|---|
| Issue-linked | squad/{issue-number}-{short-kebab-slug} |
.worktrees/{issue-number}-{short-kebab-slug} |
| Ad-hoc fix | fix/{short-kebab-slug} |
.worktrees/{short-kebab-slug} |
| Ad-hoc maintenance/docs | chore/{short-kebab-slug} or docs/{short-kebab-slug} |
.worktrees/{short-kebab-slug} |
Coordinator responsibility
Whoever spawns a local background agent for any code change MUST put explicit
worktree bootstrap commands (git fetch, git worktree add, and cd) in the spawn
prompt. Do not assume the agent will infer this requirement or allow it to default to
the shared primary checkout.
For an issue-linked task, the prompt must include commands equivalent to:
git fetch origin dev
git worktree add ".worktrees/{issue-number}-{slug}" \
-b "squad/{issue-number}-{slug}" origin/dev
cd ".worktrees/{issue-number}-{slug}"
For an ad-hoc task, the prompt must include commands equivalent to:
git fetch origin dev
git worktree add ".worktrees/{short-kebab-slug}" \
-b "fix/{short-kebab-slug}" origin/dev
cd ".worktrees/{short-kebab-slug}"
For example, two local agents that both run Git operations in the same directory can overwrite each other's checked-out branch or staged files, mixing uncommitted changes. Separate worktrees prevent that collision.
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.
- 3d ago First seen · 124 lines · 24 tokens per session scan A 64d41d6ca32c
agentweaver-git-workflow is a skill published in the GitHub repository sabbour/agentweaver (5 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 1,431 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-08-31.
Other skills, from other repositories
auditing-kubernetes-cluster-rbac
Auditing Kubernetes cluster RBAC configurations to identify overly permissive roles, wildcard permissions, dangerous ClusterRoleBindings, service account abuse, and privilege escalation paths using kubectl, rbac-tool, KubiScan, and Kubeaudit.
agent-workflow-playbook
AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4…
dotnet-microsoft-agent-framework
Build .NET AI agents and multi-agent workflows with Microsoft Agent Framework using the right agent type, threads, tools, workflows, hosting protocols, and enterprise guardrails.
dotnet-microsoft-extensions-ai
Build provider-agnostic .NET AI integrations with Microsoft.Extensions.AI, IChatClient, embeddings, middleware, structured output, vector search, and evaluation.
dotnet-orleans
Build or review distributed .NET applications with Orleans grains, silos, persistence, streaming, reminders, placement, testing, and cloud-native hosting.
mcaf-dotnet
Primary entry skill for C# and .NET tasks. Detect the repo's language version, test runner, quality stack, and architecture rules; route to the right .NET subskills; and run the repo-defined post-change quality pass after any code change. Use when the user asks to implement, debug, review, or refactor .NET code, or…