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 skills/transilienceai/communitytools/github-workflownpx skills add transilienceai/communitytools --skill github-workflowgit clone --depth 1 https://github.com/transilienceai/communitytoolsWhat 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.00044 | $0.00869 |
| Opus 5 | $0.00022 | $0.00434 |
| Sonnet 5 | $0.00009 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
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 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflow
Automate the full GitHub development lifecycle: branches, commits, pushes, PRs, issues, and code review.
Quick Start
- User requests a git action (commit, PR, branch, push, issue)
- Check repo state:
git status,git branch,git log --oneline -5 - Execute the appropriate workflow below
- Confirm result to user
Workflows
1. Branching
# Create feature branch from main
git checkout main && git pull origin main
git checkout -b <type>/<name>
# Types: feature/, bugfix/, docs/, refactor/, test/, chore/
- Always branch from up-to-date
main - Use conventional naming:
feature/add-jwt-testing,bugfix/fix-port-detection
2. Committing
# Stage specific files (never git add -A blindly)
git add <file1> <file2>
# Commit with conventional format
git commit -m "type(scope): description"
- Types:
feat,fix,docs,refactor,test,chore - Message focuses on why, not what
- Never commit
.env, credentials, or secrets - See reference/commit-conventions.md
3. Pushing
# First push (set upstream)
git push -u origin <branch-name>
# Subsequent pushes
git push
- Never force-push to
main/masterwithout explicit user approval - If push is rejected,
git pull --rebasefirst
4. Pull Requests
# Create PR linking to issue
gh pr create --title "Short title < 70 chars" --body "$(cat <<'EOF'
## Summary
- What changed and why
## Test plan
- [ ] How to verify
Fixes #<issue-number>
EOF
)"
- Title < 70 chars, details in body
- Always link to issue:
Fixes #NorCloses #N - See reference/pr-workflow.md
5. Issues
gh issue create --title "type: description" --body "$(cat <<'EOF'
## Problem
What needs to change
## Proposed solution
How to fix it
## Acceptance criteria
- [ ] Criteria 1
EOF
)"
6. Code Review
# Review a PR
gh pr view <number>
gh pr diff <number>
gh pr checks <number>
# Comment or approve
gh pr review <number> --approve
gh pr review <number> --comment --body "feedback"
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 123 lines · 44 tokens per session scan A 496b0366e62f
github-workflow is a skill published in the GitHub repository transilienceai/communitytools (498 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 869 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
pentester-playwright
Phases 1b/3/4 authorized browser automation — SPA recon, multi-role auth, route/API catalog, PoC screenshots, Evidence landing (scoped proxy). Skill-gate read for web phases. Use when Phase 1b/3/4 web work, JS-rendered SPA, real browser needed, HAR/network capture, or Playwright PoC evidence.
osint-recon
Phase 1 conditional OSINT depth — four-dimension model (server→site→domain→people; people is conditional). Skill-gate companion to pentester-enum-services / pentester-recon. Use for passive OSINT depth, full recon dimensions, author tracking, not as Phase 0/Schema replacement.
pentester-exploit
Phase 4 exploitation — PoC construction, exploit-db/msf search, safe verification. Required Skill-gate read at Phase 4. Use when starting Phase 4, exploitation, exploit, PoC, exploit-db, msf, Metasploit, or payload delivery.
pentester-toolkit
Provision the pinned pentest toolset via DotSlash for the current scanenv (host-kali or kali-target-${ID}). Adapter, not a tool wrapper.
pentester-waf-bypass
Phase 4 conditional — WAF/filter bypass for authorized CTF/range/pentest when payloads are blocked. Use at Phase 4 if blocked, or when user mentions WAF bypass, filter evasion, SQL/XSS/command-injection bypass, or security filter analysis.
pentester-recon
Phase 1 intelligence recon methodology — passive+active recon, stack fingerprint, attack-surface map. Required Skill-gate read at Phase 1 (with pentester-enum-services). Use when starting Phase 1, intelligence gathering, recon, reconnaissance, OSINT prep, target profiling, or attack surface mapping.