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/jacopalas/agentic-ai-palas/commitnpx skills add Jacopalas/agentic-ai-palas --skill commitgit clone --depth 1 https://github.com/Jacopalas/agentic-ai-palasWhat 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.00038 | $0.00933 |
| Opus 5 | $0.00019 | $0.00466 |
| Sonnet 5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
commit 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 2d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/palas-git:commit — Create Consistent Git Commits
IMPORTANT: Before starting execution, inform the user: "ESTOY EJECUTANDO EL SKILL /palas-git:commit"
Create git commits with well-structured, conventional commit messages. All commit messages MUST be written in Spanish.
Usage
/git:commit [message]
Arguments:
message(Optional): Commit message or description of changes. If omitted, analyze staged changes automatically.
Commit Message Format
Follow Conventional Commits format:
<type>(<scope>): <subject>
<body>
Types
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Formatting, no code change |
refactor |
Code restructuring, no behavior change |
perf |
Performance improvement |
test |
Adding or fixing tests |
chore |
Build, config, dependencies |
ci |
CI/CD changes |
Scope
Optional. Component or area affected (e.g., auth, api, ui).
Subject
- Imperative mood ("añade función" not "añadida función")
- No period at end
- Max 50 characters
- Always in Spanish
Body
- Explain why, not what (code shows what)
- Wrap at 72 characters
- Optional for small changes
- Always in Spanish
Behavior
- Check git status: Run
git statusto see changes - Check staged files: Run
git diff --staged --stat - Check recent commits: Run
git log --oneline -5for style reference - Analyze changes: Determine type and scope from files changed
- Draft message: Create commit message following format
- Stage if needed: Add relevant files if not staged
- Commit: Execute
git commitwith message - Verify: Run
git statusto confirm
Examples
/git:commit
-> Analyzes staged changes, drafts appropriate message in Spanish
/git:commit add user authentication
-> Creates: feat(auth): añade autenticación de usuario
/git:commit fix login redirect bug
-> Creates: fix(auth): corrige bug de redirección en login
/git:commit update README with installation steps
-> Creates: docs: actualiza README con pasos de instalación
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.
- 2d ago First seen · 144 lines · 38 tokens per session scan A b96987c4e6f1
commit is a skill published in the GitHub repository Jacopalas/agentic-ai-palas (2 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 933 once invoked, about $0.0002 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
commit
Creates semantic git commits with conventional commit format, stages selected changes safely, and optionally pushes to remote after explicit approval. Handles pre-commit hooks and writes meaningful commit messages. Use when the user says "commit", "push changes", "save to git", "commit this", or wants to create a git…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
commit
Create a git commit for the Vision-Agents repo.
commit
Commit current changes with a clear, descriptive message.
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
git-commit
Create git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead.