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/siberiacancode/agent-skills/agents-mdgit clone --depth 1 https://github.com/siberiacancode/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/siberiacancode/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/siberiacancode/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/siberiacancode/agent-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.00767 | $0.00767 |
| Opus 5 | $0.00383 | $0.00383 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
agent-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.
What it actually says
AGENTS.md
This file provides guidance to AI coding agents (Claude Code, Cursor, Copilot, etc.) when working with code in this repository.
Repository Overview
Personal collection of skills for Claude.ai and Claude Code. These skills are tailored to siberiacancode projects and packaged as instructions and scripts that extend agent capabilities.
Creating a New Skill
Directory Structure
skills/
{skill-name}/ # kebab-case directory name
SKILL.md # Required: skill definition
scripts/ # Required: executable scripts
{script-name}.sh # Bash scripts (preferred)
{skill-name}.zip # Required: packaged for distribution
Naming Conventions
- Skill directory:
kebab-case(e.g.,siberiacancode-deploy,log-monitor) - SKILL.md: Always uppercase, always this exact filename
- Scripts:
kebab-case.sh(e.g.,deploy.sh,fetch-logs.sh) - Zip file: Must match directory name exactly:
{skill-name}.zip
SKILL.md Format
---
name: { skill-name }
description:
{
One sentence describing when to use this skill. Include trigger phrases like "Deploy my app",
"Check logs",
etc.,
}
---
# {Skill Title}
{Brief description of what the skill does.}
## How It Works
{Numbered list explaining the skill's workflow}
## Usage
```bash
bash /mnt/skills/user/{skill-name}/scripts/{script}.sh [args]
```
Arguments:
arg1- Description (defaults to X)
Examples: {Show 2-3 common usage patterns}
Output
{Show example output users will see}
Present Results to User
{Template for how Claude should format results when presenting to users}
Troubleshooting
{Common issues and solutions, especially network/permissions errors}
### Best Practices for Context Efficiency
Skills are loaded on-demand — only the skill name and description are loaded at startup. The full `SKILL.md` loads into context only when the agent decides the skill is relevant. To minimize context usage:
- **Keep SKILL.md under 500 lines** — put detailed reference material in separate files
- **Write specific descriptions** — helps the agent know exactly when to activate the skill
- **Use progressive disclosure** — reference supporting files that get read only when needed
- **Prefer scripts over inline code** — script execution doesn't consume context (only output does)
- **File references work one level deep** — link directly from SKILL.md to supporting files
### Script Requirements
- Use `#!/bin/bash` shebang
- Use `set -e` for fail-fast behavior
- Write status messages to stderr: `echo "Message" >&2`
- Write machine-readable output (JSON) to stdout
- Include a cleanup trap for temp files
- Reference the script path as `/mnt/skills/user/{skill-name}/scripts/{script}.sh`
### Creating the Zip Package
After creating or updating a skill:
```bash
cd skills
zip -r {skill-name}.zip {skill-name}/
End-User Installation
Document these two installation methods for users:
Claude Code:
cp -r skills/{skill-name} ~/.claude/skills/
claude.ai: Add the skill to project knowledge or paste SKILL.md contents into the conversation.
If the skill requires network access, instruct users to add required domains at claude.ai/settings/capabilities.
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 · 120 lines · 767 tokens per session scan A 1dd1c081bdef
agent-skills AGENTS.md is an instructions file published in the GitHub repository siberiacancode/agent-skills (18 stars, last pushed yesterday), licensed MIT. It adds 767 tokens to every session, about $0.0038 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
reactuse CLAUDE.md
Claude Code instructions for childrentime/reactuse, covering reactuse - project guidelines, project overview, development, generated api docs and ai agent system (.claude/).
NextRanger AGENTS.md
AGENTS.md instructions for ihabkhaled/NextRanger, covering agents.md — universal agent entrypoint, read first, in this order, non-negotiables digest, skills routing table and validation commands.
NextRanger GEMINI.md
Gemini CLI instructions for ihabkhaled/NextRanger, covering gemini.md, repo purpose, stack, commands and architecture layers.
NextRanger CLAUDE.md
Claude Code instructions for ihabkhaled/NextRanger, covering claude.md, stack, commands, architecture digest and hard rules digest.
AI-Nextjs-Monorepo-Starter copilot-instructions.md
Copilot instructions for IvanTsxx/AI-Nextjs-Monorepo-Starter, covering ultracite code standards, quick reference, core principles, type safety & explicitness and modern javascript/typescript.
AI-Nextjs-Monorepo-Starter GEMINI.md
Gemini CLI instructions for IvanTsxx/AI-Nextjs-Monorepo-Starter, covering ultracite code standards, quick reference, core principles, type safety & explicitness and modern javascript/typescript.