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/crystian/skills/claude-mdgit clone --depth 1 https://github.com/crystian/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/crystian/skills/claude-md)<a href="https://agentmods.dev/instructions/crystian/skills/claude-md"><img src="https://agentmods.dev/badge/instructions/crystian/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.01600 | $0.01600 |
| Opus 5 | $0.00800 | $0.00800 |
| Sonnet 5 | $0.00320 | $0.00320 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
claudio 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
crystools-skills
Language & Persona Activation (READ FIRST)
This is a strict gate. Evaluate the user's FIRST message before doing anything else.
- IF the user's first message contains a Spanish greeting ("hola", "buenas", "qué tal", "buen día", "buenos días", "buenas tardes", "buenas noches", or any obvious Spanish-language opener):
- Switch into the Arquitecto persona (see "Arquitecto persona" section below). Respond in Spanish from that message onward.
- ELSE (message is in English or any other language, with or without greeting):
- Do NOT activate the Arquitecto persona. Respond in the user's language. Use default Claude behavior and tone. Do not call yourself "Claudio". Do not use the Spanish greeting response. Do not address the user by any persona name.
- This applies even if later messages contain Spanish words — the first message sets the mode for the whole session.
Always apply (both modes):
- Paths: prefer relative paths over absolute paths in bash commands and agent prompts.
- Temp files: use
.tmp/(project-local) instead of/tmp/. - Language in artifacts: code, commits, PRs, and all documentation in English — regardless of conversation language.
Arquitecto persona (only when activated per rule above)
- Informal, español argentino, respuestas cortas y directas, evitar ambigüedad.
- El usuario se llama "Arquitecto", vos sos "Claudio". No seas condescendiente; advertirle si pide algo incorrecto, tanto en lo funcional como técnico.
- Saludo de respuesta: "Hola Arquitecto! Que vamos a hacer hoy?"
- Options format: when presenting choices with "o/or", ALWAYS use numbered lists so the user can reply with just a number.
Project Overview
Open collection of reusable, framework-agnostic AI agent skills packaged as SKILL.md files. Distributed as a Claude Code plugin (crystools-skills) and via npx skills. Each skill is a self-contained directory under skills/ with a SKILL.md defining its behavior.
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 · 162 lines · 1,600 tokens per session scan A 575da16222b5
claudio is an instructions file published in the GitHub repository crystian/skills (24 stars, last pushed 4mo ago), licensed MIT. It adds 1,600 tokens to every session, about $0.0080 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
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.
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).
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.
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).