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 instructions/future-architect/uzomuzo-oss/git-workflowgit clone --depth 1 https://github.com/future-architect/uzomuzo-ossWhat 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.01493 | $0.01493 |
| Opus 5 | $0.00746 | $0.00746 |
| Sonnet 5 | $0.00299 | $0.00299 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
uzomuzo-oss git-workflow.instructions.md 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 today.
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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Commit Message Format
<type>: <description>
<optional body>
Types: feat, fix, refactor, docs, test, chore, perf, ci
Branch Protection Policy
NEVER push directly to main. All changes MUST go through a pull request, no matter how small. Create a branch, push it, and open a PR. Ask the user before merging.
Pull Request Workflow
When creating PRs:
- Create a feature/fix/chore branch from main
- Analyze full commit history (not just latest commit)
- Use
git diff [base-branch]...HEADto see all changes - Draft comprehensive PR summary
- Include test plan with TODOs
- For behavior-changing PRs, include a Runtime verification section with real evidence — see below
- Push with
-uflag if new branch
Runtime verification — always paste real evidence in the PR body
A behavior-changing PR (new feature, bug fix, or a refactor that alters runtime behavior) must include a "Runtime verification" section in the PR body that pastes the actual commands you ran and the output you observed (logs, file/DB state, exit codes, etc.).
- Unit tests passing plus static analysis alone does NOT count as "verified". Run the real binary / real environment at least once and observe the headline behavior actually happening.
- A path that is hard to unit-test because of concrete dependencies can still be observed end-to-end with the real binary plus a small forced scenario (e.g., run the target once against a temporary fixture, seed the prior state / input so the target branch is exercised, then inspect the logs and resulting state).
- Only when runtime verification is genuinely impossible, state the reason and the residual risk explicitly. Do not defer the headline behavior's verification to a runbook and use that as the primary evidence.
Branch Isolation with Git Worktree
Multiple Claude Code sessions or terminals may run concurrently in the same repository. To prevent branch switching conflicts, always use git worktree for feature branch work.
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.
- today First seen · 151 lines · 1,493 tokens per session scan A f123f5c80b35
uzomuzo-oss git-workflow.instructions.md is an instructions file published in the GitHub repository future-architect/uzomuzo-oss (32 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,493 tokens to every session, about $0.0075 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-01.
Other instructions, from other repositories
sq AGENTS.md
Instructions for neilotoole/sq, covering agents.md, about sq, key documents, common commands and conventions.
cli AGENTS.md
Instructions for planetscale/cli, covering planetscale cli — agent guide, public repository safety, concepts, flag placement and correct.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
gorest AGENTS.md
Instructions for pilinux/gorest, covering agents.md, project overview, build and run commands, build and tidy dependencies.
chatgpt-cli CLAUDE.md
Instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
pvetui AGENTS.md
Instructions for devnullvoid/pvetui, covering agent instructions, initial setup, development workflow, quick reference and code quality standards.