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/alirezasoltanijazi/skillnir/devopsengineernpx skills add AlirezaSoltaniJazi/Skillnir --skill devopsengineergit clone --depth 1 https://github.com/AlirezaSoltaniJazi/SkillnirWhat 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.00107 | $0.03228 |
| Opus 5 | $0.00053 | $0.01614 |
| Sonnet 5 | $0.00021 | $0.00646 |
| Haiku 4.5 | $0.00011 | $0.00323 |
Grade A, and why
devopsEngineer 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before You Start
Read LEARNED.md first. It contains corrections, preferences, and conventions accumulated from previous sessions. Apply every rule in that file — they override defaults in this skill.
Announce skill usage. Always say "Using: devopsEngineer skill" at the very start of your response before doing any work.
When to Use
- Creating or modifying GitHub Actions workflows under
.github/workflows/ - Configuring pre-commit hooks in
.pre-commit-config.yaml - Updating linter/formatter configuration (
.pylintrc, Black flags, autoflake args) - Writing or modifying bash validation scripts under
.data/skills/*/scripts/ - Modifying CI-related sections of
pyproject.toml(build system, dev dependencies) - Creating composite actions under
.github/actions/
Do NOT Use
- Python source code (modules, dataclasses, CLI logic) — use backendEngineer
- NiceGUI UI components/pages (Tailwind, Quasar) — use frontendEngineer
- Skill system meta-rules (SKILL.md structure, LEARNED.md format) — use skillnir
Architecture
.github/
├── actions/setup-python/action.yml # Composite: Python 3.14 + pip cache
├── workflows/
│ ├── run-tests.yml # pytest --tb=short -q
│ ├── check-style.yml # Black → Autoflake → Pylint → Bandit
│ └── auto-assign-author.yml # PR author assignment
└── pull_request_template.md # Summary + Changes + Test plan
.pre-commit-config.yaml # 11 hooks mirroring CI checks
.pylintrc # 500+ line comprehensive config
pyproject.toml # hatchling build, uv, dev deps
Flow: Code change → pre-commit hooks (local) → git push → GitHub Actions CI (remote) → PR merge decision.
Key Patterns
What ships with it
14 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.
- agents/hook-debugger.md 1.7 KB
- agents/pipeline-reviewer.md 1.8 KB
- agents/security-scanner.md 1.7 KB
- assets/pre-commit-hook-example.yaml 694 B
- assets/workflow-example.yml 776 B
- INJECT.md 829 B
- LEARNED.md 198 B
- references/ai-interaction-guide.md 3.1 KB
- references/code-style.md 3.2 KB
- references/common-issues.md 3.4 KB
- references/deployment-guide.md 3.8 KB
- references/pipeline-patterns.md 4.6 KB
- references/security-checklist.md 2.9 KB
- scripts/validate-infra.sh 4.1 KB runs code
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 · 210 lines · 107 tokens per session scan A e10496303536
devopsEngineer is a skill published in the GitHub repository AlirezaSoltaniJazi/Skillnir (7 stars, last pushed 1mo ago), licensed MIT. It adds 107 tokens to every session and 3,228 once invoked, about $0.0005 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.