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/mindbox-cloud/agent-skills/claude-mdgit clone --depth 1 https://github.com/mindbox-cloud/agent-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/mindbox-cloud/agent-skills/claude-md)<a href="https://agentmods.dev/instructions/mindbox-cloud/agent-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/mindbox-cloud/agent-skills/claude-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.01143 | $0.01143 |
| Opus 5 | $0.00571 | $0.00571 |
| Sonnet 5 | $0.00229 | $0.00229 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
agent-skills CLAUDE.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 4d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-skills — Developer Guide for Claude Code
Repository Purpose
This is a public marketplace of Claude Code plugins by mindbox.cloud. Each plugin extends Claude Code with skills (slash commands), agents, hooks, or MCP servers.
Plugins are designed to be shared with the community. All content must be in English.
Repository Structure
agent-skills/
├── .claude-plugin/
│ └── marketplace.json # marketplace registry — update when adding a plugin
├── plugins/
│ └── <plugin-name>/
│ ├── .claude-plugin/
│ │ └── plugin.json # plugin manifest
│ ├── skills/
│ │ └── <skill-name>/
│ │ ├── SKILL.md
│ │ └── references/
│ ├── CHANGELOG.md
│ └── README.md
├── CLAUDE.md
├── CONTRIBUTING.md
└── README.md
How to Add a New Plugin
Step 1 — Create the directory structure
mkdir -p plugins/<plugin-name>/.claude-plugin
mkdir -p plugins/<plugin-name>/skills/<skill-name>/references
Plugin names: kebab-case, no spaces.
Step 2 — Write plugin.json
{
"name": "plugin-name",
"description": "One-line description in English",
"version": "1.0.0",
"author": {
"name": "Author or org name"
}
}
Required fields: name. Recommended: description, version, author.
Step 3 — Write SKILL.md
---
name: skill-name # kebab-case, matches folder name
description: >
What it does — one sentence.
Use when user says "...", "...", "...".
Don't use when: user asks for X (use y-skill instead), user asks for Z.
metadata:
version: 1.0.0 # semver — instruction contract version
---
Skill body: orchestration logic, steps, critical rules, troubleshooting.
Put domain knowledge and checklists in references/, not inline.
Frontmatter requirements:
name— kebab-case, 1–64 chars, matches folder namedescription— WHAT it does + WHEN to use (trigger phrases) + "Don't use when" (negative triggers)metadata.version— semver
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.
- 4d ago First seen · 163 lines · 1,143 tokens per session scan A 79f8b38113b4
agent-skills CLAUDE.md is an instructions file published in the GitHub repository mindbox-cloud/agent-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 1,143 tokens to every session, about $0.0057 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.
Other instructions, from other repositories
embedded-systems-architect AGENTS.md
Instructions for Zachariah9420/embedded-systems-architect: This repository ships an agent skill for embedded-systems and edge-AI development work.
pbnz-skills AGENTS.md
AGENTS.md instructions for PBNZ/pbnz-skills, covering agents.md — pbnz-skills, start-here map — where things live and ground rules.
qa-orchestra CLAUDE.md
Claude Code instructions for Anasss/qa-orchestra, covering qa orchestra — claude code instructions, what this project is, quick start, 1. clone into your workspace and 2. fill in your project context.
claude-sdlc CLAUDE.md
Claude Code instructions for lantisprime/claude-sdlc, covering claude.md, what this repo is, design intent — read this before "improving" anything, eat your own dog food and hook strictness philosophy.
claude-account-switch AGENTS.md
AGENTS.md instructions for LightZirconite/claude-account-switch, covering claude + codex account switch - agent guide, product invariants, authentication ux, switching safety and provider parity and deliberate differences.
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).