skern AGENTS.md

Repository instructions for skern, a Go command-line tool that stores and manages reusable instructions for coding agents in SKILL.md files. It describes the project structure, supported commands, and development decisions.

In plain words
What is it for?
Use it when developing skern, especially for registry commands such as creating, importing, searching, validating, showing, comparing, or removing skills.
Why use it?
It gives an agent the project context and rules it needs before changing skern, reducing guesswork about where code belongs and how it should be checked.

Instructions file for CodexOpenCode

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/devrimcavusoglu/skern/agents-md
Clone the repo
git clone --depth 1 https://github.com/devrimcavusoglu/skern

Made for: Codex, OpenCode.

Per session 4,349 This file is loaded in full into every session.
When invoked 4,349 The same file — it is already loaded in full.
Security scan B 1 finding. 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.04349 $0.04349
Opus 5 $0.02174 $0.02174
Sonnet 5 $0.00870 $0.00870
Haiku 4.5 $0.00435 $0.00435

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

Security

Grade B, and why

skern AGENTS.md scanned grade B with 1 finding 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 2d 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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

| Per-platform capacity (project scope) | Count in the platform's project skills dir (e.g. `.claude/skills/`) | Warn at >= 20 |
AGENTS.md · 376 lines

How it starts

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

AGENTS.md — Skern Development Guide

Conventions, architecture, and design decisions for agents working in this repo. Human contributor setup — the full build/test matrix, directory tree, and dependency list — lives in docs/contributing/development.md. Release history lives in CHANGELOG.md; neither is restated here.

Project Overview

Skern is a minimal, agent-first CLI for managing Agent Skills across agentic development platforms. It follows the Agent Skills open standard (agentskills.io) and uses SKILL.md files with YAML frontmatter as the canonical format.

Written in Go 1.25+. Latest release v0.4.0; main carries unreleased work (see the [Unreleased] section of the CHANGELOG).

Scope

The registry is the center of gravity. Skern's value is being the single cross-platform source of truth for skills: one SKILL.md per skill, stored once, managed through skern regardless of which agent is running. Registry commands (create, import, edit, list, search, show, validate, version, diff, recommend, remove) are the primary surface, and skern init --instructions exists so an agent can be told to reach for skern directly instead of hunting through platform directories.

Platform install/uninstall is first-class and stays. Copying skills out to native platform directories serves real cases the registry alone does not: native progressive disclosure, sandboxed agents that cannot shell out to skern, and one-shot migration from an existing .claude/skills/. Adapters are maintained and extended, and adapter bugs are ordinary product bugs — they are just not the headline drive. The skern skill command tree encodes this split directly via two cobra groups: Registry commands and Platform commands (internal/cli/skill.go).

When proposing features, weigh them against the registry thesis first. New work that only makes sense as a per-platform copy needs a use case from the list above.

Read the full file on GitHub · 376 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. 2d ago First seen · 376 lines · 4,349 tokens per session scan B 87464af57700

Subscribe to this mod's changes

skern AGENTS.md is an instructions file published in the GitHub repository devrimcavusoglu/skern (7 stars, last pushed 12d ago), licensed Apache-2.0. It adds 4,349 tokens to every session, about $0.0217 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.