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/abdullahkhawer/devops-skills/create-skillnpx skills add abdullahkhawer/devops-skills --skill create-skillgit clone --depth 1 https://github.com/abdullahkhawer/devops-skillsWrote 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/abdullahkhawer/devops-skills/create-skill)<a href="https://agentmods.dev/skills/abdullahkhawer/devops-skills/create-skill"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/create-skill.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 | $0.00022 | $0.00567 |
| Opus 5 | $0.00011 | $0.00283 |
| Sonnet 5 | $0.00004 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
create-skill 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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Skill
Run this skill when asked to create a new skill from a conversation or description of a task.
Step 1 — Gather requirements
Ask the user only these two questions:
1. What specific task or problem do you want this skill to solve?
2. What are the specific instructions and guidelines for this task?
Wait for the user's answers before proceeding.
Step 2 — Determine skill name and location
Derive a short, lowercase, hyphenated skill name from the task description (e.g. deploy-lambda, check-postgres-health).
Ask the user which AI agent they are using, then use the corresponding path:
| Agent | Skill path |
|---|---|
| Claude Code | .claude/skills/<skill-name>/SKILL.md |
| GitHub Copilot | .github/skills/<skill-name>/SKILL.md |
| Other | skills/<skill-name>/SKILL.md |
Create the directory if it does not exist:
mkdir -p <path-to-skill-dir>
Step 3 — Write the SKILL.md file
Use the template below, filling in all <...> placeholders based on the user's answers.
---
name: <skill-name>
description: <One-liner description of what this skill does.>
---
# <Skill Title>
Run this skill when asked to <task statement>.
## Step 1 — <First step title>
<Instructions for the first step.>
## Step 2 — <Second step title>
<Instructions for the second step.>
...
## Rules
- <Rule 1>
- <Rule 2>
Guidelines for writing the skill
- Each step should have a clear title and concrete instructions or commands.
- Include bash commands in fenced code blocks where relevant.
- Rules section must cover safety constraints, error handling, and edge cases.
- Keep the skill focused — one skill, one workflow.
- Do not include secrets, credentials, or hardcoded environment-specific values.
Step 4 — Confirm with the user
After writing the file, show the user the generated SKILL.md content and the path where it was saved. Ask if any adjustments are needed.
Rules
- Always place the skill in the correct path for the user's AI agent (see Step 2 table).
- The skill name must be lowercase and hyphenated.
- Never include credentials, API tokens, or secrets in the generated skill.
- If the user's description is too vague to produce actionable steps, ask clarifying questions before writing the file.
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.
- 4d ago First seen · 95 lines · 22 tokens per session scan A 4ef2824b851a
create-skill is a skill published in the GitHub repository abdullahkhawer/devops-skills (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 567 once invoked, about $0.0001 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
docs-manage
Manage the Grounded Docs MCP Server documentation index. Covers scraping and indexing documentation from URLs or local files, refreshing existing indexes with changed content, and removing libraries from the index. Use when you need to add, update, or delete indexed documentation.
docs-search
Search and query the Grounded Docs MCP Server documentation index. Covers listing indexed libraries, searching documentation content, and resolving library versions. Use when you need to look up API references, find code examples, or check which documentation is available in the local index.
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
lore
SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all your agent harnesses. Use when the user…
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
live-exercise
Use whenever any UI-bearing work touches a running instance — building or fixing a feature, ship-gating, auditing, OR debugging visible bugs (flaky behavior, intermittent rendering, "sometimes does X" reports, hover/focus/animation glitches, layout overflow). Adaptive depth from tactical fix-loop to ship-gate audit.…