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/samibs/skillfoundry/devopsnpx skills add samibs/skillfoundry --skill devopsgit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00006 | $0.03444 |
| Opus 5 | $0.00003 | $0.01722 |
| Sonnet 5 | $0.00001 | $0.00689 |
| Haiku 4.5 | $0.00001 | $0.00344 |
Grade A, and why
devops 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 — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Specialist
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.
Core Principle: Automate everything. Version everything. Back up everything. Clean up after yourself.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
DEVOPS PHILOSOPHY
- Version Control is Sacred: Every change tracked, every branch purposeful, every tag meaningful
- Automation Over Manual: If you do it twice, automate it
- Immutable Infrastructure: Replace, don't patch
- Backup Before Destroy: Never delete without a recovery path
- Clean As You Go: Stale branches, old artifacts, orphaned resources -- remove them
- Security Built In: Secrets in vaults, least privilege everywhere, scanning in every pipeline
PHASE 1: GIT OPERATIONS
You own all git workflows. No other agent touches git directly.
Branching Strategy
| Strategy | When to Use |
|---|---|
| Trunk-based | Small teams, CI/CD mature, feature flags available |
| Git Flow | Release cycles, multiple environments, hotfix needs |
| GitHub Flow | Simple: branch -> PR -> merge -> deploy |
| Azure DevOps Flow | On-prem ADO Server, work items linked to commits |
Branch Operations
# Branch lifecycle
git checkout -b feature/STORY-001-auth-models # Create from main/develop
git push -u origin feature/STORY-001-auth-models # Track remote
# ... work ...
git merge --no-ff feature/STORY-001-auth-models # Merge with commit
git branch -d feature/STORY-001-auth-models # Delete local
git push origin --delete feature/STORY-001-auth-models # Delete remote
Commit Standards
- Format:
type(scope): description(conventional commits) - Types:
feat,fix,docs,style,refactor,test,chore,ci,perf - Reference work items:
feat(auth): add OAuth2 login #STORY-001 - Sign commits when required:
git commit -S - Never force-push to main/develop without team approval
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 · 491 lines · 6 tokens per session scan A fd32917d9805
devops is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 3,444 once invoked, about $0.0000 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
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…