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 omnigentx/jarvis --skill git-workflowgit clone --depth 1 https://github.com/omnigentx/jarvisWrote 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/omnigentx/jarvis/git-workflow)<a href="https://agentmods.dev/skills/omnigentx/jarvis/git-workflow"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/git-workflow/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/omnigentx/jarvis/git-workflow"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00333 |
| Opus 5.5 | $0.00013 | $0.00133 |
| Sonnet 5.5 | $0.00006 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
git-workflow 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.
What it actually says
GIT WORKFLOW
Branch strategy
main (production)
├── develop (staging)
│ ├── feature/add-dark-mode
│ ├── feature/new-agent-card
│ ├── bugfix/fix-calendar-dup
│ └── hotfix/fix-auth-crash
Branch naming
feature/<short-description>— new featurebugfix/<short-description>— bug fixhotfix/<short-description>— urgent prod fix
Commit conventions
<type>(<scope>): <description>
Types: feat, fix, docs, refactor, test, chore
Scope: backend, frontend, skills, infra
Examples:
feat(backend): add finance decision tree skillfix(frontend): fix agent card overflow on mobilerefactor(skills): merge system-design into architecture
Pull request template
## What
[Short description]
## Why
[Reason for the change]
## How
[Approach / technical details]
## Testing
- [ ] Unit tests pass
- [ ] Manual testing done
## Screenshots (if UI)
Rules
- Commit often, with clear messages.
- One PR = one feature or bug fix.
- Rebase before merging (no merge commits).
- DO NOT push directly to main.
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 · 64 lines · 32 tokens per session scan A 23030445e054
git-workflow is a skill published in the GitHub repository omnigentx/jarvis (39 stars, last pushed 11d ago), licensed MIT. It adds 32 tokens to every session and 333 once invoked, about $0.0001 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…