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 Jacopalas/agentic-ai-palas --skill commitgit clone --depth 1 https://github.com/Jacopalas/agentic-ai-palasWrote 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/jacopalas/agentic-ai-palas/commit)<a href="https://agentmods.dev/skills/jacopalas/agentic-ai-palas/commit"><img src="https://agentmods.dev/badge/skills/jacopalas/agentic-ai-palas/commit/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/jacopalas/agentic-ai-palas/commit"><img src="https://agentmods.dev/badge/skills/jacopalas/agentic-ai-palas/commit.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.00038 | $0.00933 |
| Opus 5.5 | $0.00015 | $0.00373 |
| Sonnet 5.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 1mo 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.
- 1mo 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 21d ago), licensed MIT. It adds 38 tokens to every session and 933 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
commit
Create a conventional commit and optionally push it safely.
create-commit
Compose and create a git commit whose message follows the Angular Conventional Commits standard, so semantic-release can version and changelog it automatically. Use this skill whenever the user wants to commit staged changes, "make a commit", "commit this", "write a commit message", "commit with conventional/angular…
conventional-commits
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
smart-commit
A Git skill that uses an AI language model to summarize code changes and suggest commit messages. Git is a tool for recording changes to code.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
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.