salvar

salvar is a skill for Claude Code, Codex from felipenalves/InvOS. It costs 59 tokens per session (668 once invoked), scanned A, original, MIT.

A one-command Git workflow that saves the current project to GitHub, an online service for storing and sharing code. It can set up the repository the first time and push later changes.

In plain words
What is it for?
Use it when you say “salvar”, “commit”, “push”, or “/salvar” to initialize a repository, create commits, and push the project to GitHub.
Why use it?
It removes the need to remember the Git commands for creating commits, linking a GitHub repository, and uploading changes. It also provides a backup of the project.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it when you say “salvar”, “commit”, “push”, or “/salvar” to initialize a repository, create commits, and push the project to GitHub.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/felipenalves/invos/salvar
Install

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.

Any agent
npx skills add felipenalves/InvOS --skill salvar
Clone the repo
git clone --depth 1 https://github.com/felipenalves/InvOS

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for salvar

README.md
[![agentmods](https://agentmods.dev/badge/skills/felipenalves/invos/salvar.svg)](https://agentmods.dev/skills/felipenalves/invos/salvar)
Your own site
<a href="https://agentmods.dev/skills/felipenalves/invos/salvar"><img src="https://agentmods.dev/badge/skills/felipenalves/invos/salvar.svg" alt="Measured on agentmods" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 668 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.00668
Opus 5 $0.00030 $0.00334
Sonnet 5 $0.00012 $0.00134
Haiku 4.5 $0.00006 $0.00067

Measured 7d ago against content hash 607db706b4c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

salvar 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 7d 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.

.agents/skills/salvar/SKILL.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/salvar — Salvar no GitHub

Skill de uma função só: garantir que o trabalho do usuário está no GitHub. Fácil pra quem nunca usou git.

Workflow

Primeira vez (repositório não inicializado)

Detectar com git rev-parse --is-inside-work-tree. Se falhar:

  1. Perguntar:

    "Esse é o primeiro sync. Você já tem um repositório criado no GitHub pra esse workspace?

    1. Sim, me passa a URL (ex: https://github.com/usuario/nome.git)
    2. Não, vou criar agora — me dá um nome pro repositório (ex: meu-invos)"
  2. Se opção 1: rodar git init, git add ., git commit -m "Setup inicial do INVOS", git branch -M main, git remote add origin <URL>, git push -u origin main.

  3. Se opção 2: verificar se o gh CLI está instalado (gh --version).

    • Se sim: rodar git init, criar commit inicial, e gh repo create <nome> --private --source=. --push.
    • Se não: instruir o usuário a instalar gh (https://cli.github.com/) ou criar o repo manualmente em github.com/new e voltar com a URL.

Commits seguintes (já configurado)

  1. Rodar git status. Se não tiver mudanças, responder "Tá tudo sincronizado, sem mudança nova" e parar.

  2. Mostrar o git status curto pro usuário e perguntar:

    "Vou comitar tudo isso. Quer descrever a mudança em uma frase ou usa o resumo automático?"

  3. Se o usuário fornecer mensagem, usar. Se não, gerar uma mensagem baseada nos arquivos alterados (1 linha, formato: "Atualiza X" ou "Adiciona Y" ou "Cria proposta pra cliente Z").

  4. git add .git commit -m "<mensagem>"git push.

  5. Confirmar com link do repositório (extrair de git remote get-url origin):

    "Sincronizado. Ver no GitHub: "

Regras

  • Nunca usar --force sem o usuário pedir explicitamente
  • Nunca rodar git reset --hard ou outras destrutivas sem confirmação clara
  • Se o push falhar por divergência (remoto tem commits — inclusive no primeiro push, quando o GitHub criou README/licença), avisar o usuário e oferecer git pull --rebase antes de tentar de novo
  • Se o usuário ainda não tiver git configurado (user.name / user.email), perguntar e configurar com git config --global na primeira vez

Read the full file on GitHub · 50 lines

Changes

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.

  1. 7d ago First seen · 50 lines · 59 tokens per session scan A 607db706b4c9

Subscribe to this mod's changes

salvar is a skill published in the GitHub repository felipenalves/InvOS (5 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 668 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

adk-git

Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and testing-plan sections the PR template requires. Use when writing or rewording a commit message, squashing commits before a…

google/adk-python · 138 tokens

git-advanced-workflows

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

wshobson/agents · 54 tokens

commit-context

Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.

rohitg00/agentmemory · 61 tokens

commit-history

List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.

rohitg00/agentmemory · 49 tokens

workflow-patterns

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

wshobson/agents · 35 tokens

block-no-verify-hook

Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.

wshobson/agents · 46 tokens