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.
git clone --depth 1 https://github.com/ArogyaReddy/alirezarezvani-claude-skillsWrote 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/commands/arogyareddy/alirezarezvani-claude-skills/readme)<a href="https://agentmods.dev/commands/arogyareddy/alirezarezvani-claude-skills/readme"><img src="https://agentmods.dev/badge/commands/arogyareddy/alirezarezvani-claude-skills/readme/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/commands/arogyareddy/alirezarezvani-claude-skills/readme"><img src="https://agentmods.dev/badge/commands/arogyareddy/alirezarezvani-claude-skills/readme.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.00000 | $0.01825 |
| Opus 5 | $0.00000 | $0.00912 |
| Sonnet 5 | $0.00000 | $0.00365 |
| Haiku 4.5 | $0.00000 | $0.00183 |
Grade A, and why
README 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 10d 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.
This is a copy
100% identical to README — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Skills Slash Commands
Git workflow and quality assurance commands for the claude-skills repository.
🎯 Essential Commands
Git Workflow
/git:cm → Stage and commit (no push)
/git:cp → Stage, commit, and push
/git:pr → Create pull request
/git:clean → Delete merged branches (local + remote)
Quality Gates
/review → Run local quality checks
/security-scan → Run security validation
/update-docs → Post-creation sync (CLI platforms, marketplace, docs, GitHub Pages)
📋 Git Commands
/git:cm - Commit (No Push)
Purpose: Stage changes and create a conventional commit without pushing
Usage:
/git:cm
What it does:
- Shows
git status --short - Reviews each file diff for secrets
- Stages files intentionally
- Generates conventional commit message
- Creates commit (no push)
When to use: When you want to commit locally before pushing
/git:cp - Commit and Push
Purpose: Complete git workflow with quality checks
Usage:
/git:cp
What it does:
- Runs
/reviewfor quality checks - Stages changes
- Creates conventional commit
- Pushes to origin
- Triggers CI workflows
When to use: When ready to publish changes
/git:pr - Create Pull Request
Purpose: Create a PR from current branch
Usage:
/git:pr # PR to main
/git:pr dev # PR to dev branch
What it does:
- Verifies quality checks passed
- Creates PR using template
- Adds appropriate labels
- Shares PR link
When to use: After pushing changes and ready for review
🔒 Quality Commands
/review - Local Quality Gate
Purpose: Run all quality checks before pushing
Usage:
/review
What it checks:
- ✅ YAML linting (workflows)
- ✅ GitHub workflow schema validation
- ✅ Python syntax (all skill directories)
- ✅ Markdown link validation
- ✅ Dependency security audit (optional)
When to use: Before committing/pushing 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.
- 10d ago First seen · 352 lines · 0 tokens per session scan A 778f4b834409
README is a command published in the GitHub repository ArogyaReddy/alirezarezvani-claude-skills (31 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,825 tokens. A static security scan graded it A with 0 findings. It is 100% identical to README, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.