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 wednesday-solutions/ai-agent-skills --skill wednesday-gitgit clone --depth 1 https://github.com/wednesday-solutions/ai-agent-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/skills/wednesday-solutions/ai-agent-skills/wednesday-git)<a href="https://agentmods.dev/skills/wednesday-solutions/ai-agent-skills/wednesday-git"><img src="https://agentmods.dev/badge/skills/wednesday-solutions/ai-agent-skills/wednesday-git/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/wednesday-solutions/ai-agent-skills/wednesday-git"><img src="https://agentmods.dev/badge/skills/wednesday-solutions/ai-agent-skills/wednesday-git.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.00035 | $0.00742 |
| Opus 5 | $0.00017 | $0.00371 |
| Sonnet 5 | $0.00007 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
wednesday-git 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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wednesday Git Workflow (GIT-OS)
This skill manages the complete lifecycle of a feature or fix. It ensures that every branch, commit, and PR follows the project's quality and automation standards.
Lifecycle Phases
1. Starting a Task (sprint)
When a dev provides a ticket and wants to start working:
- Action: Create a branch following the
type/nameformat (e.g.,feat/user-auth). - Rule: Max 40 characters, kebab-case, no ticket numbers in the branch name.
- Tool:
Bash(git checkout -b <branch_name>)
2. Committing Changes (git-os)
When code is ready for an atomic commit:
- Format:
type(scope?): Description(e.g.,feat(auth): Add login endpoint). - Types:
feat,fix,refactor,perf,docs,style,test,chore. - Atomic Rule: One logical change per commit. If you've done multiple things, split them into separate commits.
- Human-Authored: NEVER include AI attribution or fingerprints.
- Linting: Before committing, ensure
npx --no-install commitlintwould pass.
3. Opening a Pull Request (pr-create)
When the task is finished and ready for review:
- Pre-Push Checklist: Run
npm run lint,format:check,test, andbuild. - Validation:
- Max 6 files per PR: If the PR is larger, suggest splitting it.
- Conventional Title: Title must match
type(scope): Description.
- Metadata: Extract ticket ID from branch name (e.g.,
WED-142). - PR Description Template:
### Ticket Link --- ### Description --- ### Steps to Test --- ### GIFs (if applicable) --- - Push & Create:
Bash(git push origin <branch>)Bash(gh pr create --title "<title>" --body "<body>")using the template above.
🚫 Never
- Direct Commits: Never commit directly to
mainordevelop. - Dirty History: Never bundle multiple concerns into one commit.
- Skip Checks: Never open a PR without running the full pre-push checklist.
- AI Fingerprints: Never use "AI-generated" descriptions or co-author tags.
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.
- 11d ago First seen · 70 lines · 0 tokens per session scan A 4639e3b341f3
wednesday-git is a skill published in the GitHub repository wednesday-solutions/ai-agent-skills (168 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 742 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-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-commit
Git commit message generator that creates conventional commit messages based on code changes.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
version-control
Manage Git repositories and collaborative workflows — branching strategies, commit hygiene, conflict resolution, pull requests, hooks, and .gitignore management. Use when the user requests version control or provides relevant inputs for this workflow.