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/scitix/siclaw/skill-authoringnpx skills add scitix/siclaw --skill skill-authoringgit clone --depth 1 https://github.com/scitix/siclawWrote 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/scitix/siclaw/skill-authoring)<a href="https://agentmods.dev/skills/scitix/siclaw/skill-authoring"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/skill-authoring.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.00040 | $0.01071 |
| Opus 5 | $0.00020 | $0.00535 |
| Sonnet 5 | $0.00008 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
skill-authoring 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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Authoring Guide
Read this guide before creating a new skill or improving an existing one.
Directory Layout
A skill is a directory package, not a single file. The smallest valid skill is:
<skill-name>/
└── SKILL.md
Optional package files can live beside SKILL.md:
<skill-name>/
├── SKILL.md
├── scripts/ # executable .sh/.py helpers
├── references/ # markdown docs the agent can read
├── examples/ # example inputs/outputs
└── assets/ # small images or other package assets
The directory name must match the name field in SKILL.md. Use uppercase
SKILL.md; lowercase skill.md is not canonical.
SKILL.md Format
---
name: <kebab-case-name>
description: >-
One-line summary. Mention the execution tool if the skill uses scripts.
---
Followed by markdown body:
# <Title>
## Purpose
What problem this skill solves and when to use it.
## Tool
<execution tool invocation — required for script-based skills>
Example: local_script: skill="check-pod-oom", script="check.sh", args="<ns> <pod>"
## Parameters
| Parameter | Required | Description |
|-----------|----------|-------------|
| `<arg1>` | Yes | ... |
## Procedure
Step-by-step actions with concrete commands.
## Examples
Concrete tool invocations with realistic parameters.
Script Execution Modes
| Tool | Runs where | When to use |
|---|---|---|
local_script |
AgentBox (local) | kubectl commands from outside the cluster — most common |
host_script |
A host via SSH | Host-level tools on a node reachable via SSH. Preferred over node_script — runs over SSH with no debug pod (lighter, leaves the node untouched) |
node_script |
K8s node (host) | Host tools, /proc, /sys, devices, nsenter. The fallback when the node is not an SSH host, or whenever a pod's netns is needed |
pod_script |
Inside a pod | Diagnostics inside a running container |
node_script + pod |
Node + pod's network ns | Host tools + pod's network view (pass pod= — node + netns resolved automatically) |
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.
- 5d ago First seen · 102 lines · 40 tokens per session scan A ad16a201e087
skill-authoring is a skill published in the GitHub repository scitix/siclaw (232 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 1,071 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
ariadne-kubernetes-graph
Use for Ariadne MCP-backed Kubernetes state questions: translate operational questions into Cypher, repair graphquery failures, and decide when graphschema or graphhealth is needed. Best for live or snapshot-backed graph data about resource relationships; do not use for codebase-only tasks or generic Kubernetes…
k8s-service-connectivity
Service 连通性问题通常由 Endpoints 缺失、Selector 不匹配、[[networkpolicy|NetworkPolicy]] 阻断或 kube-proxy 异常引起。.
k8s-deployment-rollout
Kubernetes Deployment 发布失败、滚动更新卡住的完整诊断-修复-验证 Skill.
k8s-pod-crashloop
Pod CrashLoopBackOff / OOMKilled 诊断与修复：Pod CrashLoopBackOff 和 OOMKilled 是 Kubernetes 工作负载中最常见的问题类型。本 Skill 覆盖从症状识别到修复验证的完整闭环。.
k8s-dns-failure
DNS 解析问题诊断与修复：CoreDNS 是 Kubernetes 集群 DNS 的核心组件。DNS 问题会导致服务发现失败、外部依赖不可访问等连锁问题。.
k8s-control-plane
Control Plane Failure：API entities/etcd.md/Scheduler 问题的诊断与修复 Skill。.