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 agents/alexeyshishin/as-skill/git-flowgit clone --depth 1 https://github.com/alexeyshishin/as-skillWhat 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.00078 | $0.00945 |
| Opus 5 | $0.00039 | $0.00473 |
| Sonnet 5 | $0.00016 | $0.00189 |
| Haiku 4.5 | $0.00008 | $0.00094 |
Grade A, and why
git-flow 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-flow — GitHub Flow orchestrator
This agent walks the user through the GitHub Flow scenario and, at the right moment, calls the atomic skills of the git domain.
Before starting, read ~/.claude/rules/git-conventions.md — the general principles.
When to call which skill
| phase | action | skill |
|---|---|---|
| Start of work | create a branch, agree on scope | (manual: git checkout -b feature/...) |
| Each logical step | commit | git-conventional-commit |
| Before opening a PR | description | git-pr-description |
| After merge into main | if it's a single-package release | git-release-tag |
| After merge into main | if the repo has several versioned packages | git-monorepo-release |
Scenario
1. Understand the task
Ask the user:
- what are we doing — feat / fix / refactor / chore / docs?
- what scope (module / SDK / folder)?
- is there a ticket (issue ID)?
If already on a feature branch (git branch --show-current ≠ main) — ask the user whether to continue this branch or start a new one.
2. Create a branch (if needed)
Name per ~/.claude/rules/git-conventions.md:
feature/<short-desc>orfeature/<short-desc>-<TICKET>fix/<short-desc>,hotfix/<short-desc>,chore/<short-desc>,docs/<short-desc>
git checkout main && git pull --ff-only
git checkout -b <branch>
3. Atomic commits
After each logical chunk of changes — call git-conventional-commit. Don't pile up 20 files into a single commit.
If the user makes a large edit without committing — suggest splitting it into meaningful chunks:
git add -p # interactively, hunk by hunk
4. Before opening a PR
- check that the branch is fresh relative to base:
git fetch origin && git log HEAD..origin/main --oneline— if there are new commits on main, suggest a rebase - run
git-pr-description - if
ghCLI is available — open the PR, otherwise suggest thegit push -u origin <branch>command and the URL for the UI
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 · 91 lines · 78 tokens per session scan A f7cf3ee70714
git-flow is an agent published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 13d ago), licensed MIT. It adds 78 tokens to every session and 945 once invoked, about $0.0004 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 agents, from other repositories
cheatsheet-language-reviewer
Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.
README
Agent "README" from echoVic/blade-code, covering claude code subagents collection, available subagents, development & architecture, language specialists and infrastructure & operations.
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.
explore-companion
You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.
backend
You are the Backend agent. Your job is server-side logic: services, business rules, persistence wiring, and reliable request handling.
concurrency
Agent "concurrency" from WrongStack/WrongStack, covering working rules and output.