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 skills/pyramidheadshark/claude-scaffold/skill-developernpx skills add pyramidheadshark/claude-scaffold --skill skill-developergit clone --depth 1 https://github.com/pyramidheadshark/claude-scaffoldWrote 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/skills/pyramidheadshark/claude-scaffold/skill-developer)<a href="https://agentmods.dev/skills/pyramidheadshark/claude-scaffold/skill-developer"><img src="https://agentmods.dev/badge/skills/pyramidheadshark/claude-scaffold/skill-developer.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.00000 | $0.00851 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
skill-developer 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Developer
When to Load This Skill
Load when: creating a new skill, modifying an existing skill, updating skill-rules.json, evaluating skill quality, or refactoring the skill library.
Skill Anatomy
Every skill follows this structure:
.claude/skills/{skill-name}/
├── SKILL.md # main file — MUST be under 500 lines
└── resources/
├── topic-1.md # deep-dive subsections — under 500 lines each
└── topic-2.md
SKILL.md is the entry point. It must:
- State when to load the skill (trigger criteria)
- Provide immediately actionable patterns (not just theory)
- Reference
resources/files for details rather than inlining everything - Stay under 500 lines — if growing beyond this, extract to resources
Creating a New Skill
Step 1: Define the trigger
Ask: "What file patterns or prompt keywords make this skill relevant?"
These go into skill-rules.json under the skill's triggers.
Step 2: Write SKILL.md
Structure:
# {Skill Name}
## When to Load This Skill
{file patterns and keywords}
## {Core Concept or Setup}
{immediately actionable content}
## {Main Pattern 1}
{code example or steps}
## {Main Pattern 2}
{code example or steps}
## Further Resources
Step 3: Register in skill-rules.json
{
"skill": "my-new-skill",
"triggers": {
"files": ["*.relevant-ext", "specific-file.py"],
"keywords": ["relevant keyword", "another trigger phrase"],
"always_load": false
},
"priority": 11
}
Priority determines load order when the 3-skill limit is reached. Lower number = higher priority.
Step 4: Test activation
Open a test project, mention a trigger keyword, and verify the skill appears in context via the hook output.
Quality Standards
A good skill is:
- Actionable: Contains copy-paste-ready code, not just descriptions
- Specific: Covers our actual stack (uv, FastAPI, YC, etc.) not generic patterns
- Concise: Every line earns its place — no padding
- Self-contained: Does not require reading another skill to use
- Honest: Notes limitations and when NOT to use the pattern
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 118 lines · 0 tokens per session scan A 46896b099274
skill-developer is a skill published in the GitHub repository pyramidheadshark/claude-scaffold (4 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 851 tokens. 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 skills, from other repositories
mle-workflow
Production ML engineering workflow — data contracts, reproducible training, evaluation gates, deployment, and monitoring. Use when building, reviewing, or hardening ML systems beyond notebooks.
data-scientist
!cat Claude-Production-Grade-Suite/.protocols/ux-protocol.md 2>/dev/null || true !cat Claude-Production-Grade-Suite/.protocols/input-validation.md 2>/dev/null || true !cat Claude-Production-Grade-Suite/.protocols/tool-efficiency.md 2>/dev/null || true !cat Claude-Production-Grade-Suite/.protocols/visual-identity.md…
ai-engineer
Builds production AI/ML systems — model training, fine-tuning, MLOps pipelines, model serving, evaluation frameworks, RAG optimization, and agent orchestration at scale. Use when the user asks to build, train, or deploy ML models, set up MLOps pipelines, optimize RAG systems, create inference endpoints, or design…
data-scientist
!cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat .production-grade.yaml 2>/dev/null || echo "No config — using defaults".
ai-ml-engineering
AI/ML Engineering Review: Reviews AI/ML systems for production readiness — model serving, MLOps pipelines, LLM integration patterns, prompt engineering, evaluation frameworks, and responsible AI. Covers model deployment, feature stores, experiment tracking, monitoring/drift detection, and AI safety. Use when the user…
git-hooks-manager
Setup and manage git hooks for pre-commit, pre-push automation (lint, test, format).