Borrowing it
Nothing to install: this file belongs to Kilo-Org/kilo-marketplace. 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/Kilo-Org/kilo-marketplace/main/AGENTS.mdgit clone --depth 1 https://github.com/Kilo-Org/kilo-marketplaceWrote 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/kilo-org/kilo-marketplace/agents-md)<a href="https://agentmods.dev/instructions/kilo-org/kilo-marketplace/agents-md"><img src="https://agentmods.dev/badge/instructions/kilo-org/kilo-marketplace/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.1 | $0.00788 | $0.00788 |
| Opus 5 | $0.00394 | $0.00394 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
kilo-marketplace 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Documentation
This document describes how skills should be structured in this repository.
What is a Skill?
Skills are modular, self-contained packages that extend an agent's capabilities by providing specialized knowledge, workflows, and tools. They transform a general-purpose agent into a specialized agent equipped with procedural knowledge for specific domains or tasks.
Skill Directory Structure
Every skill consists of a required SKILL.md file and optional bundled resources:
skill-name/
├── SKILL.md # Required - Main skill definition
├── LICENSE # Recommended - License terms
├── scripts/ # Optional - Executable code (Python/Bash/etc.)
├── references/ # Optional - Documentation loaded into context as needed
├── assets/ # Optional - Files used in output (templates, icons, fonts)
└── examples/ # Optional - Example files demonstrating usage
SKILL.md Structure
Note on Contributed Skills
All contributed skills must reference an external repository in the metadata.source section of the SKILL.md frontmatter. The Kilo Marketplace does not host the source code for third-party skills directly. See CONTRIBUTING.md for details and examples.
Frontmatter (Required)
Every SKILL.md file must begin with YAML frontmatter containing metadata:
---
name: skill-name
description: A clear description of what the skill does and when it should be used. Use third-person (e.g., "This skill should be used when...").
license: MIT # Either license or license_path is required, not both
metadata:
category: development # or business, etc.
author: author-name # Optional - who created the skill
source: # Optional - for skills from external sources
repository: https://github.com/org/repo
path: path/to/skill/in/repo
license_path: path/to/LICENSE # Path to LICENSE in source repo (alternative to license)
commit: 0123456789abcdef0123456789abcdef01234567 # Imported revision
---
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.
- 8d ago First seen · 76 lines · 788 tokens per session scan A 9a7b5e141e00
kilo-marketplace AGENTS.md is an instructions file published in the GitHub repository Kilo-Org/kilo-marketplace (173 stars, last pushed 18d ago), licensed Apache-2.0. It adds 788 tokens to every session, about $0.0039 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
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.