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/eljulians/skillfile/claude-mdgit clone --depth 1 https://github.com/eljulians/skillfileWrote 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/eljulians/skillfile/claude-md)<a href="https://agentmods.dev/instructions/eljulians/skillfile/claude-md"><img src="https://agentmods.dev/badge/instructions/eljulians/skillfile/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.01815 | $0.01815 |
| Opus 5 | $0.00907 | $0.00907 |
| Sonnet 5 | $0.00363 | $0.00363 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
skillfile 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 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skillfile Development Guide
This file is for maintainers and contributors using Claude Code or similar coding agents in this repository. Keep changes aligned with the public project contract in README.md and SPEC.md.
Project Shape
skillfile is a Rust workspace CLI for managing AI skill and agent markdown files. It reads a Skillfile, fetches upstream content, locks exact revisions, preserves local edits as patches, and deploys to supported AI tool directories.
Workspace dependency direction is strict:
core <- sources <- deploy <- cli
crates/core: models, parsing, lock files, conflicts, patches, output, errors.crates/sources: HTTP clients, GitHub/GitLab/registry resolution, sync logic.crates/deploy: platform adapters and install orchestration.crates/cli: clap commands, TUI flows, update checks, binary entrypoint.tests: workspace-level functional tests that spawn the CLI.fuzz: parser fuzz target, excluded from the normal workspace.
Architecture Standards
- Keep domain models and format rules in
core; do not letcoredepend on network, deployment, terminal UI, or command concerns. - Keep source fetching and registry behavior in
sources; do not bypassHttpClientwhen code needs to be testable. - Keep platform-specific filesystem layout behind
PlatformAdapter; avoid hardcoded per-tool branching in command code. - Keep CLI code as orchestration and presentation. Reusable behavior belongs in the lower crate that owns the concept.
- Preserve backward compatibility for
Skillfile,Skillfile.lock, patch paths, and installed layout unlessSPEC.mdis updated in the same change. - Prefer typed domain errors in library crates via
SkillfileError; reserveanyhowfor top-level CLI reporting. - Do not add broad abstractions for hypothetical future platforms, sources, or entity types. Add extension points when a concrete second use case exists.
- When changing a public contract, include the migration story, docs update, and tests that lock the new 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 · 132 lines · 1,815 tokens per session scan A ffb6c1b23b2b
skillfile CLAUDE.md is an instructions file published in the GitHub repository eljulians/skillfile (143 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,815 tokens to every session, about $0.0091 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
awesome-qa-skills AGENTS.md
AGENTS.md instructions for naodeng/awesome-qa-skills, covering agents.md, project overview, repository map (edit here), skill.md conventions and agents/openai.yaml.
ux-ui-agent-skills CLAUDE.md
Claude Code instructions for sterlingpathological200/ux-ui-agent-skills, covering ux/ui expert agent — claude design system skill, decision framework, design principles, atomic design and design thinking.
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.
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.
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.