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 JansenAnalytics/claudex --skill github-workflowgit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/github-workflow)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/github-workflow"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/github-workflow.svg" alt="Measured on agentmods" 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.00310 |
| Opus 5 | $0.00017 | $0.00155 |
| Sonnet 5 | $0.00007 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
github-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 3d 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
GitHub Workflow
Tools
- gh CLI:
~/.local/bin/gh— authenticated as JansenAnalytics - git: Standard git commands
Rules
- Feature branches always. Never push to main directly.
fixes #Nin commits auto-closes issues.refs #Ndoes not.- Use conventional commit messages when appropriate.
Common Commands
# PR operations
gh pr create --title "..." --body "..."
gh pr list
gh pr status
gh pr merge <number>
# Issues
gh issue create --title "..." --body "..."
gh issue list --label "bug"
# CI/Actions
gh run list
gh run view <id> --log-failed
# Repo
gh repo create JansenAnalytics/<name> --private
gh repo clone JansenAnalytics/<name>
Key Repos
prop-hedge-agents— Trading system (branch: feature/agent-restructure)prop-hedge-dashboard— Dashboard (branch: master)brewboard— BCH analytics (branch: feature/frontend-polish)
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.
- 3d ago First seen · 45 lines · 35 tokens per session scan A e0f6c7c6a787
github-workflow is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 310 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-09-03.
Other skills, from other repositories
github-manager
GitHub operations - manage issues, pull requests, repositories, and workflows via GitHub API.
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.
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
commit-staged
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
ship-it
A GitHub workflow for finishing an implemented issue: commit the relevant changes, push a branch, create a pull request, merge it, and close the issue. GitHub is a service for hosting code and reviewing changes, and a pull request is a proposed change for review.