skills AGENTS.md

Repository instructions for maintaining biw/skills, a collection of installable tools for AI agents. They describe where skills go, how they are documented, and how to validate them.

In plain words
What is it for?
Use them when adding, documenting, testing, validating, or checking discoverability of skills in the repository.
Why use it?
They give contributors one shared set of rules, reducing inconsistent skill structure, missing documentation, and untested helpers.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/biw/skills/agents-md
Clone the repo
git clone --depth 1 https://github.com/biw/skills

Made for: Codex, OpenCode.

Per session 261 This file is loaded in full into every session.
When invoked 261 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00261 $0.00261
Opus 5 $0.00130 $0.00130
Sonnet 5 $0.00052 $0.00052
Haiku 4.5 $0.00026 $0.00026

Measured 2d ago against content hash 56625f1a49fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

AGENTS.md · 16 lines

What it actually says

Repository Instructions

This repository publishes Agent Skills from biw/skills.

  • Put installable skills under skills/<skill-name>/SKILL.md.
  • When adding an installable skill, add it to the README's Available Skills list with a link and concise description.
  • Start from both templates under templates/skill/, including agents/openai.yaml.tmpl.
  • Keep the name frontmatter exactly equal to the parent folder name.
  • Write descriptions as clear trigger surfaces in 200 characters or fewer.
  • Keep starter material under templates/ with .tmpl suffixes so the CLI does not publish it.
  • Add scripts, references, and assets only when they directly support a skill; test executable helpers.
  • The skill installer copies every file below skills/<skill-name>/ except a few metadata/cache paths. Keep development tests exclusively under tests/<skill-name>/; never place *.test.* or *.spec.* files inside an installable skill directory.
  • Run pnpm validate before committing skill changes.
  • Use pnpm skills add . --list to smoke-test CLI discovery after at least one skill exists.
  • Do not commit scratch repos or generated output. .context/ is for local agent collaboration only.
Changes

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.

  1. 2d ago First seen · 16 lines · 261 tokens per session scan A 56625f1a49fd

Subscribe to this mod's changes

skills AGENTS.md is an instructions file published in the GitHub repository biw/skills (2 stars, last pushed 9d ago), licensed MIT. It adds 261 tokens to every session, about $0.0013 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.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens