Borrowing it
Nothing to install: this file belongs to timwukp/agent-skills-best-practice. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/timwukp/agent-skills-best-practice/main/.kiro/steering/conventions.mdgit clone --depth 1 https://github.com/timwukp/agent-skills-best-practiceWrote 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/timwukp/agent-skills-best-practice/conventions)<a href="https://agentmods.dev/instructions/timwukp/agent-skills-best-practice/conventions"><img src="https://agentmods.dev/badge/instructions/timwukp/agent-skills-best-practice/conventions.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.00484 | $0.00484 |
| Opus 5 | $0.00242 | $0.00242 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
agent-skills-best-practice conventions.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 yesterday.
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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Standards and Conventions
Language
- All documentation must be written in English.
Agent Skills Specification Compliance
- Skill names must be kebab-case (lowercase letters, digits, and hyphens only) and must match the skill's directory name.
- Skill descriptions must not exceed 1024 characters, must be written in the third person, and should state both what the skill does and when to use it (with concrete trigger phrases).
- Skill descriptions must not contain angle brackets (
<or>). - Every skill directory must contain a
SKILL.mdfile with valid YAML frontmatter includingnameanddescriptionfields. - Keep the
SKILL.mdbody under 500 lines; move detailed reference material into separate files within the skill folder (progressive disclosure). - Skills must conform to the Agent Skills Specification.
Python
- Python scripts must be compatible with Python 3.10+.
- Dependencies are listed in
requirements.txtat the repository root.
SKILL.md Frontmatter
All SKILL.md files must begin with YAML frontmatter containing at minimum:
---
name: my-skill-name
description: A concise description of what this skill does.
---
Allowed frontmatter properties: name, description, license, allowed-tools, metadata, compatibility.
Workshop Materials
Workshop chapters follow a consistent structure with these files:
slides.md- Presentation contentexercises.md- Hands-on exercisesexamples.md- Example implementationstemplates.md- Reusable templatestest-cases.md- Validation test cases
Repository Rules
- No binary document files (PDF, PPTX, DOCX, or similar) in the repository.
- No PII or customer data in any file.
- No hardcoded credentials or secrets in code or configuration.
- New content is licensed under the MIT License; skills imported from anthropics/skills remain Apache 2.0 (see each skill's
LICENSE.txt). Do not add content under non-open-source licenses.
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.
- yesterday First seen · 54 lines · 484 tokens per session scan A 675c6df20f38
agent-skills-best-practice conventions.md is an instructions file published in the GitHub repository timwukp/agent-skills-best-practice (10 stars, last pushed 2d ago), licensed MIT. It adds 484 tokens to every session, about $0.0024 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-09-06.
Other instructions, from other repositories
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.