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 instructions/knocklabs/skills/agents-mdgit clone --depth 1 https://github.com/knocklabs/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/instructions/knocklabs/skills/agents-md)<a href="https://agentmods.dev/instructions/knocklabs/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/knocklabs/skills/agents-md.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.01292 | $0.01292 |
| Opus 5 | $0.00646 | $0.00646 |
| Sonnet 5 | $0.00258 | $0.00258 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
skills AGENTS.md 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
How to add new skills and rules
This guide explains how to structure and add new skills to this repository.
Skill structure
Each skill should follow this structure:
skills/
└── knock-your-skill-name/
├── SKILL.md # Human-readable guide (required)
└── rules/ # Rule files directory (required)
├── rule-1.md
├── rule-2.md
└── ...
Step-by-step guide
1. Create the skill directory
Create a new directory under skills/ with a descriptive name using the knock- prefix and kebab-case:
mkdir -p skills/knock-your-skill-name/rules
2. Create rule files
Add individual rule files in the rules/ directory. Each rule file should:
- Use markdown format (
.md) - Include frontmatter with metadata:
--- title: Your rule title description: Brief description of the rule tags: - relevant-tag-1 - relevant-tag-2 category: knock-your-skill-name last_updated: YYYY-MM-DD --- - Use sentence case for all titles and headings
- Be focused on a single topic or theme
- Include examples and practical guidance
Example rule file structure:
---
title: Rule name in sentence case
description: What this rule covers
tags:
- tag1
- tag2
category: knock-your-skill-name
last_updated: 2026-01-23
---
# Rule name in sentence case
## Section heading
Content here...
### Subsection
More content...
3. Create SKILL.md
Create a SKILL.md file that serves as a human-readable guide. It should:
- Provide an overview of the skill
- Explain how to use the different rules
- Reference rule files using relative paths (e.g.,
rules/rule-1.md) - Include quick reference sections
- Use sentence case for all headings
Example SKILL.md structure:
---
name: knock-your-skill-name
description: Brief description of what this skill provides.
---
# Your skill name
Brief description of what this skill provides.
## Overview
List the rule files and what they cover.
## How to use this skill
### For specific use case 1
1. **Start with rule X** (`rules/rule-x.md`)
- What to look for
- Key principles
2. **Check rule Y** (`rules/rule-y.md`)
- Additional considerations
## Rule files reference
- `rules/rule-1.md` - Description
- `rules/rule-2.md` - Description
## Quick reference
Key points and 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.
- 5d ago First seen · 214 lines · 1,292 tokens per session scan A f95b53720d6a
skills AGENTS.md is an instructions file published in the GitHub repository knocklabs/skills (0 stars, last pushed yesterday), licensed MIT. It adds 1,292 tokens to every session, about $0.0065 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.