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 joaoguirunas/team-os --skill dev-git-workflowgit clone --depth 1 https://github.com/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/dev-git-workflow)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/dev-git-workflow"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/dev-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/joaoguirunas/team-os/dev-git-workflow"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/dev-git-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.01621 |
| Opus 5.5 | $0.00012 | $0.00648 |
| Sonnet 5.5 | $0.00006 | $0.00324 |
| Haiku 4.5 | $0.00003 | $0.00162 |
Grade A, and why
dev-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 27d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow — Software Complexo
Branch Strategy
⚠️ Regra dura — branch de publicação: antes de qualquer
push/PR/merge, pergunte em qual branch publicar; amainé o padrão prioritário. Nunca crie branch nova nem assuma a branch atual por conta própria. Só usefeature/*(ou outra) quando o usuário pedir explicitamente — nesse caso vale a nomenclatura abaixo.
main → padrão de publicação, produção, sempre estável
├── feature/ → novas features SÓ quando o usuário pedir (ex: feature/42-user-auth)
├── fix/ → bugfixes sob demanda (ex: fix/login-null-pointer)
├── hotfix/ → urgente produção, parte de main
└── chore/ → deps, config, infra
Nomenclatura (quando branch for solicitada): {type}/{issue-id}-{slug} — ex: feature/42-user-authentication
Conventional Commits
Formato: type(scope): descrição imperativa em inglês
| Type | Quando usar |
|---|---|
feat |
Nova funcionalidade |
fix |
Correção de bug |
refactor |
Mudança sem feature nem fix |
test |
Adicionar/corrigir testes |
chore |
Deps, config, build |
docs |
Documentação |
perf |
Melhoria de performance |
ci |
CI/CD |
Exemplos:
feat(auth): add JWT refresh token rotation
fix(api): handle null response from payment provider
test(auth): add token expiration edge cases
chore(deps): upgrade Next.js to 15.2.0
Regras:
- Imperativo, minúsculo, sem ponto final
- Scope identifica o módulo (
auth,api,ui,db) - Breaking change:
feat(api)!: rename user endpoint - Referenciar story no rodapé:
Story: docs/smart-memory/stories/active/2.3-titulo.md
Autoridade de Git
| Operação | Quem pode |
|---|---|
git add, git commit |
Todos os devs |
git branch, git checkout |
Todos os devs |
git diff, git log, git status |
Todos os agentes |
git merge (local) |
Todos os devs |
git push |
EXCLUSIVO dev-devops (Grav) |
gh pr create/merge |
EXCLUSIVO dev-devops (Grav) |
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.
- 27d ago Changed 9cfa34b22068
- 1mo ago First seen · 179 lines · 30 tokens per session scan A 2a196cf91f51
dev-git-workflow is a skill published in the GitHub repository joaoguirunas/team-os (5 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 1,621 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-09-03.
Other skills, from other repositories
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
git-workflow
Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
git-pushing
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
github-activity
Report what happened across GitHub repositories over a time window, read only. Invoke when the user asks what merged, which issues were opened or closed, or what moved between milestones since a date or since the last report, across one or more repositories.
implement-issue
Turn one labelled GitHub issue into one reviewed pull request, or stop with a stated reason. Use for every factory run; the message is a link to the issue.