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/practicalswan/agent-skills/devops-toolingnpx skills add PracticalSwan/agent-skills --skill devops-toolinggit clone --depth 1 https://github.com/PracticalSwan/agent-skillsWhat 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.00042 | $0.05384 |
| Opus 5 | $0.00021 | $0.02692 |
| Sonnet 5 | $0.00008 | $0.01077 |
| Haiku 4.5 | $0.00004 | $0.00538 |
Grade C, and why
devops-tooling scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$TEMP_DIR" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
for cmd in curl jq az; do How it starts
The opening of the file, as written. The whole thing — 1,078 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devops Tooling
Comprehensive toolkit for Git workflows, shell scripting, and development automation.
- Leverage native parallel subagent dispatch and 200k+ context windows where available.
When to Use This Skill
Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
- Creating conventional commits and managing Git workflows
- Writing Bash, Zsh, or PowerShell automation scripts
- Configuring CI/CD pipelines (GitHub Actions, Azure DevOps)
- Automating development, testing, or deployment tasks
- Troubleshooting Git conflicts and repository hygiene issues
Part 1: Git Workflows
Conventional Commits
The conventional commit specification provides an easy-to-extend set of rules for creating an explicit commit history.
Commit Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types
| Type | Purpose | Example |
|---|---|---|
feat |
New feature | feat(auth): add OAuth2 support |
fix |
Bug fix | fix(api): resolve null reference |
docs |
Documentation only | docs(readme): update setup guide |
style |
Formatting/style (no logic) | style(ui): fix indentation |
refactor |
Refactor production code | refactor(svc): extract helpers |
perf |
Performance improvement | perf(db): add index on email |
test |
Adding tests | test(auth): add unit tests |
build |
Build system or deps | build(ci): upgrade Node to v20 |
ci |
CI configuration changes | ci(github): add workflow for PRs |
chore |
Maintenance tasks | chore(deps): update packages |
revert |
Revert previous commit | revert: feat(login) |
Breaking Changes
Breaking changes must be indicated by ! after the type/scope, or via BREAKING CHANGE in footer:
feat(api)!: remove deprecated v1 endpoint
feat(api): remove deprecated v1 endpoint
BREAKING CHANGE: v1 endpoints are no longer supported. Use v2.
Good Examples
What ships with it
6 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.
- 3d ago First seen · 1,078 lines · 42 tokens per session scan C ca317a01c908
devops-tooling is a skill published in the GitHub repository PracticalSwan/agent-skills (11 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 5,384 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
atomic-commit
Atomic git workflow - validates, commits, pushes, creates PR/MR, and verifies CI with zero-warnings policy. Orchestrates complete code submission as state machine with rollback on failure. Supports GitHub (gh) and GitLab (glab). Triggers: "commit changes", "push and create PR", "submit code", "atomic commit".
ship-it
Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh). Triggers after a goal (GitHub Issue) implementation is complete — commit code, push branch, create PR, merge, then close the issue. Use when the user says "提交代码", "commit and merge", "创建PR", "合入", "关闭issue", "ship-it", or when a goal…
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
safe-workflow
SAFe development workflow guidance including branch naming conventions, commit message format, rebase-first workflow, and CI validation. Use when starting work on a Linear ticket, preparing commits, creating branches, writing PR descriptions, or asking about contribution guidelines.
cicd
CI/CD reference for Megatron Bridge — pipeline structure, commit and PR workflow, CI failure investigation, and common failure patterns.
gza-task-improve
Address feedback for a gza task inline — reads review findings and/or unresolved comments, checks out the branch, fixes must-fix items and comments, runs verify, and commits.