agentmods.dev

skilly CLAUDE.md

A project guide for skilly, a self-hosted company registry for managing agent skill files. It explains the project structure, development commands, and the rule that the main specification must be updated first.

In plain words
What is it for?
Use it when working on skilly’s codebase, especially when locating key files, following its development workflow, or checking changes against the project specification.
Why use it?
It gives a coding agent the project context needed before changing code. This helps keep implementation decisions, versioning, changelog entries, and the fixed installation format consistent.

Instructions file

4 6d ago A scan 3,413 tokens original Apache-2.0
View the source file scalefocus/skilly
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/scalefocus/skilly/claude-md
Clone the repo
git clone --depth 1 https://github.com/scalefocus/skilly
Per session 3,413 This file is loaded in full into every session.
When invoked 3,413 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.03413 $0.03413
Opus 5 $0.01707 $0.01707
Sonnet 5 $0.00683 $0.00683
Haiku 4.5 $0.00341 $0.00341

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

Security

Grade A, and why

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

CLAUDE.md · 188 lines

How it starts

The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — skilly project context

Read this first. It pins the project's intent, decisions, conventions, and the single most important constraint. The authoritative spec is SKILLY_SPEC.md; this file is the working context for day-to-day implementation. §n references throughout this file are the canonical deep-dive pointers into SKILLY_SPEC.md.

What this is

skilly — an enterprise-grade, open-source, self-hosted registry for governing Anthropic-style SKILL.md agent skills across an organization and its business units, with identity/access anchored in Microsoft Entra ID. Greenfield, SKILL.md-compatible. Apache 2.0.

Key files (jump straight here)

File Role
SKILLY_SPEC.md The authoritative spec — every change lands here first
packages/shared/src/version.ts APP_VERSION — bumped on every app change
packages/web/src/app/whats-new/changelog.ts The What's new CHANGELOG — one entry per version bump
packages/shared/src/external-tool.ts The pinned install wire format — the ONLY place it may change
packages/web/e2e/shots.mjs Playwright script that captures Quick-start / manual screenshots (manual built ad-hoc, outside the repo)
db/migrations/ Plain-SQL migrations, applied in order by the migrate compose service
deploy/docker-compose.yml The full stack (postgres, migrate, minio, clamav, web, worker, proxy)

The change workflow (GATED — spec-first with a mandatory stop)

Every change to app behavior goes through this gate. Never skip straight to code.

  1. Grill first. Before touching anything, interrogate the request rigorously: ask pointed clarifying questions — scope, edge cases, roles affected, visibility implications, data model impact, what happens on expiry/deletion/conflict — until the requirement is unambiguous. Depth is proportional to the change (a copy fix needs one confirming question; a new feature needs a real interview). Do not assume answers you could ask for.
  2. Update SKILLY_SPEC.md — and ONLY the spec. Write the behavior, data, and contracts into the relevant sections. No code, no migrations, no manual edits yet.
  3. STOP for verification. Present the spec diff (what changed, where, and the decisions it encodes) and end the turn. The user must review and approve the spec before anything is built. Do not proceed on silence; wait for explicit go-ahead. If the user amends the spec, loop back to step 1/2 as needed.
  4. Implement to match the approved spec. Code follows spec, never the reverse. New code ships with its tests in the same change: unit tests for any new domain/RBAC/semver/validation logic, integration tests for anything touching the API, DB, or SCIM surface, and e2e coverage when the change alters a user-facing flow (propose→review→publish→install and the like). Untested new code is an incomplete implementation, not a follow-up.
  5. Release ritual. Version bump → changelog → commit (see the "Before every commit" checklist below).

Read the full file on GitHub · 188 lines

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 · 188 lines · 3,413 tokens per session scan A 3e14448a99cf

Subscribe to this mod's changes

skilly CLAUDE.md is an instructions file published in the GitHub repository scalefocus/skilly (4 stars, last pushed 6d ago), licensed Apache-2.0. It adds 3,413 tokens to every session, about $0.0171 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-31.

agent-skillsai-agentsclaudeentra-idnextjsregistry
Related

Other instructions, from other repositories

data-table-filters CLAUDE.md

Instructions for openstatusHQ/data-table-filters, covering claude.md, project overview, monorepo structure (pnpm + turborepo), key commands and database.

openstatusHQ/data-table-filters · 1,088 tokens

www-sacred AGENTS.md

Instructions for internet-development/www-sacred, covering agents.md, what this repo is, repo map, conventions and the fonts menu previews.

internet-development/www-sacred · 3,243 tokens

karakeep CLAUDE.md

Claude Code instructions for karakeep-app/karakeep, a project described as: A self-hostable bookmark-everything app (links, notes and images) with AI-based automatic tagging and full text search.

karakeep-app/karakeep · 3 tokens

Codex-Skills AGENTS.md

Instructions for TheGoat395/Codex-Skills, covering repository operating notes, required checks, evidence rules and change hygiene.

TheGoat395/Codex-Skills · 294 tokens

souls-directory CLAUDE.md

Instructions for thedaviddias/souls-directory, covering claude.md — project context for ai assistants, project overview, tech stack, critical rules and database is convex.

thedaviddias/souls-directory · 1,675 tokens

agentgram CLAUDE.md

Instructions for agentgram/agentgram, covering claude.md — agentgram development guide, project overview, tech stack, monorepo structure and core architecture patterns.

agentgram/agentgram · 4,467 tokens