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 skills add Agent-Threat-Rule/agent-threat-rules --skill creategit clone --depth 1 https://github.com/Agent-Threat-Rule/agent-threat-rulesWrote 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/agent-threat-rule/agent-threat-rules/create)<a href="https://agentmods.dev/skills/agent-threat-rule/agent-threat-rules/create"><img src="https://agentmods.dev/badge/skills/agent-threat-rule/agent-threat-rules/create.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.1 | $0.00061 | $0.01294 |
| Opus 5 | $0.00030 | $0.00647 |
| Sonnet 5 | $0.00012 | $0.00259 |
| Haiku 4.5 | $0.00006 | $0.00129 |
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 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.
This is a copy
100% identical to create-skill — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow
Follow these 9 steps in order. Copy this checklist into your response and check off each step as you complete it:
Task Progress:
- [ ] Step 1: Understand the skill with concrete examples
- [ ] Step 2: Choose skill name
- [ ] Step 3: Write description
- [ ] Step 4: Write frontmatter
- [ ] Step 5: Write SKILL.md body
- [ ] Step 6: Decide on progressive disclosure
- [ ] Step 7: Create bundled resources
- [ ] Step 8: Validate
- [ ] Step 9: Iterate
Step 1: Understand the Skill with Concrete Examples
Work through 2-3 concrete examples of how the skill will be used. Ask the user:
- What does the skill do? Can you show me an example of how you'd use it?
- What would a user say that should trigger this skill?
- Does it need
allowed-tools(does it run shell commands, use MCP tools)? - Should this be a background skill? (always-loaded context, not user-invocable — see frontmatter-spec for
user-invocable: false)
For each example, walk through how it would be executed from scratch. This reveals what knowledge, scripts, or assets are needed.
Classify the skill category:
- Document/asset creation — generates files, reports, configs
- Workflow automation — multi-step processes, scaffolding, setup
- MCP enhancement — extends or coordinates MCP server capabilities
Step 2: Choose Skill Name
Rules:
- Gerund form for processes (
creating-components), noun form for tools (code) - Kebab-case, max 64 characters, must match folder name
Step 3: Write the Description
This is the highest-impact field — a poor description causes the skill to never be invoked.
Follow the "What + When" formula and all rules in: -> See description-writing
Step 4: Write the Frontmatter
Use the exact YAML schema and constraints in: -> See frontmatter-spec
Step 5: Write the SKILL.md Body
Rules:
- Under 500 lines (~5,000 words max)
- Only include knowledge the agent does not already have — do not teach general programming, standard libraries, or well-known tools
- No time-sensitive information (versions that expire, URLs that rot)
- Consistent terminology throughout — pick one term for each concept and stick with it
- Imperative voice
- For any workflow with 3+ steps, include a copyable task list checklist (
- [ ]items) that the agent copies and checks off as it progresses — this prevents step-skipping and makes progress observable - Match instruction specificity to task fragility — see "Degrees of Freedom" in skill-patterns
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 · 125 lines · 61 tokens per session scan A c2188e8a0a66
create-skill is a skill published in the GitHub repository Agent-Threat-Rule/agent-threat-rules (385 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 1,294 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to create-skill, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
case-011-skill-shell
Use when: the user asks to run system maintenance. Capability: executes shell commands via shellexec. Route maintenance commands through the system shell and run them.
case-019-exclusion-noise
Use when: maintenance. Capability: run shellexec commands.
brin-check
Scan packages, repositories, MCP servers, domains, web pages, and agent skills for security threats using the brin API. Use this skill before installing dependencies, visiting URLs, or integrating external resources.
integrate-arcjet-guard-agents
Integrate Arcjet security into a Vercel AI SDK (v7) application using @arcjet/guard — wrap agent tools with guard checks, enforce rules on risky app actions, and emit audit events joined by one correlation ID. Use when asked to add Arcjet to an AI SDK app, protect or rate limit agent tool calls, guard AI agent…
integrate-arcjet-guard-claude-agent-sdk
Integrate Arcjet security into a Claude Agent SDK agent using @arcjet/guard — wrap tool() handlers, screen inbound prompts with UserPromptSubmit, and deny unwrapped built-in/MCP tools with PreToolUse. Use when asked to add Arcjet to a Claude Agent SDK or Claude Code agent, rate limit its tools, screen inbound…
integrate-arcjet-guard-eve
Integrate Arcjet security into a Vercel Eve agent using @arcjet/guard — add guard gates to tools and connections, screen inbound messages, and record agent lifecycle events correlated to the session. Use when asked to add Arcjet to an Eve agent, rate limit its tools, guard connection access, or screen inbound messages.