agentmods.dev

pro-skill CLAUDE.md

A set of writing and repository instructions for maintaining designer-focused agent skills. A repository is the project folder containing its files and documentation.

In plain words
What is it for?
Use it when adding or improving skills, updating their documentation, organizing references and assets, and checking for security issues such as exposed secrets.
Why use it?
It gives contributors consistent rules for where skills belong, how their files should be structured, and how to write practical documentation safely.

Instructions file

19 +3 20d ago A scan 333 tokens copy · 100% MIT
View the source file devinilabs/pro-skill
Install

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.

agentmods
npx agentmods add instructions/devinilabs/pro-skill/claude-md
Clone the repo
git clone --depth 1 https://github.com/devinilabs/pro-skill
Per session 333 This file is loaded in full into every session.
When invoked 333 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00333 $0.00333
Opus 5 $0.00167 $0.00167
Sonnet 5 $0.00067 $0.00067
Haiku 4.5 $0.00033 $0.00033

Measured 3d ago against content hash d1d90aba01a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pro-skill 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 3d 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.

Origin

This is a copy

100% identical to Skills CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 50 lines

What it actually says

Claude Code — Repo Guide

Repo: @MengTo/Skills

This repo contains designer-focused AgentSkills for reusable agent workflows.

What to do here

  • Add new skills (new folders under agent-skills/)
  • Improve existing skills (SKILL.md + REFERENCES.md)
  • Keep docs procedural: checklists, recipes, pitfalls, workflows

Folder contract

Each skill folder should look like:

agent-skills/<category>/<skill-name>/
  SKILL.md            # required (frontmatter + steps)
  REFERENCES.md       # optional (links only)
  ARTICLE.md          # optional (long-form)
  assets/             # optional
  scripts/            # optional

Conventions:

  • SKILL.md should be concise + actionable.
  • REFERENCES.md should be links only (no big explanations).
  • Prefer copy/paste snippets and “when to use” triggers.

Style

  • Write like Meng To: skimmable, practical, confident.
  • Prefer constraints and defaults (durations, spacing, hierarchy).
  • Avoid fluff.

Safety

  • Don’t include secrets, API keys, tokens.
  • Don’t paste private client info.

Suggested workflow (for Claude)

  1. Identify the most specific skill folder.
  2. Update SKILL.md first.
  3. Add/refresh links in REFERENCES.md.
  4. Keep changes small and commit with a clear message.

Git

This folder is its own git repo. Work from:

cd /Users/mengto/clawd/@MengTo/Skills
Changes

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.

  1. 3d ago First seen · 50 lines · 333 tokens per session scan A d1d90aba01a9

Subscribe to this mod's changes

pro-skill CLAUDE.md is an instructions file published in the GitHub repository devinilabs/pro-skill (19 stars, last pushed 20d ago), licensed MIT. It adds 333 tokens to every session, about $0.0017 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Skills CLAUDE.md, differing in 0 lines, and is treated as a copy.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens