Borrowing it
Nothing to install: this file belongs to YPares/agent-skills. 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/YPares/agent-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/YPares/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/ypares/agent-skills/claude-md)<a href="https://agentmods.dev/instructions/ypares/agent-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/ypares/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.1 | $0.01421 | $0.01421 |
| Opus 5 | $0.00711 | $0.00711 |
| Sonnet 5 | $0.00284 | $0.00284 |
| Haiku 4.5 | $0.00142 | $0.00142 |
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 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to AI agents when working with code in this repository.
Project Overview
This repository is a curated collection of AI agent skills organized as a Claude Plugin marketplace. Each skill is a self-contained knowledge base combining:
- Documentation (SKILL.md + references/)
- Helper scripts (scripts/ directory)
- Templates/boilerplate (assets/ directory)
Refer to the README.md for installation instructions and usage tips.
Development Commands
Running Claude Code with Agent Configuration
# Use the justfile recipe (recommended)
just claude [args]
Why this matters: It sets the following env vars:
JJ_CONFIG: Prevents Claude from trying to invoke interactive editors (see.agent-space/jj-config.toml)AGENT_PROFILE: Isolated Nix profile for agent-specific tool installationsPATH: Ensures agent uses its own tool versions
Listing Available Commands
just --list
Repository Structure
Plugin Organization
Skills are organized into 6 plugin bundles in .claude-plugin/marketplace.json:
- jujutsu-skills:
working-with-jj,jj-todo-workflow - nix-skills:
nix-profile-manager,package-npm-nix - python-skills:
textual-builder - nushell-skills:
nushell-plugin-builder - github-skills:
github-pr-workflow - typst-skills:
typst-writer
Skill Directory Pattern
Each skill follows this structure:
<skill-name>/
├── SKILL.md # Primary knowledge base (entry point)
├── scripts/ # [Optional] Helper utilities
│ └── <utility-scripts> # Bash/Python/Nushell scripts
├── assets/ # [Optional] Templates and boilerplate
│ └── <template-name>/ # Reusable project templates
└── references/ # [Optional] Deep-dive technical documentation
└── <topic>.md # Supplementary reference materials
Key principle: SKILL.md is the starting point. References are for deep dives when needed.
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 · 194 lines · 1,421 tokens per session scan A 4b0eecaff491
agent-skills CLAUDE.md is an instructions file published in the GitHub repository YPares/agent-skills (30 stars, last pushed 9d ago), licensed MIT. It adds 1,421 tokens to every session, about $0.0071 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.