elps: Skill for Claude Code

.claude/skills/add-stdlib-package/SKILL.md

add-stdlib-package is a skill for Claude Code from luthersystems/elps. It costs 0 tokens per session (1,658 once invoked), scanned A, original, BSD-3-Clause.

A recipe for adding a new standard-library package to the ELPS interpreter. A standard-library package is built-in functionality, such as file access, cryptography, or an HTTP client, exposed to programs.

In plain words
What is it for?
Use it when adding a new built-in package under the ELPS standard library.
Why use it?
It keeps new packages consistent with the interpreter's existing package structure and loading rules. It also defines the functions, constants, and documentation the package should provide before coding begins.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is luthersystems/elps's own configuration. It tells Claude Code how to work on elps itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything elps configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is go test ./lisp/lisplib/lib<name>/... # Package tests pass.

Reuse

Borrowing it

Nothing to install: this file belongs to luthersystems/elps. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/luthersystems/elps/main/.claude/skills/add-stdlib-package/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/luthersystems/elps

Made for: Claude Code.

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

agentmods badge for add-stdlib-package

README.md
[![agentmods](https://agentmods.dev/badge/skills/luthersystems/elps/add-stdlib-package/github.svg)](https://agentmods.dev/skills/luthersystems/elps/add-stdlib-package)
Your own site
<a href="https://agentmods.dev/skills/luthersystems/elps/add-stdlib-package"><img src="https://agentmods.dev/badge/skills/luthersystems/elps/add-stdlib-package/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for add-stdlib-package

Your own site · 80×15
<a href="https://agentmods.dev/skills/luthersystems/elps/add-stdlib-package"><img src="https://agentmods.dev/badge/skills/luthersystems/elps/add-stdlib-package.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,658 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.01658
Opus 5.5 $0.00000 $0.00663
Sonnet 5.5 $0.00000 $0.00332
Haiku 4.5 $0.00000 $0.00166

Measured 2d ago against content hash 993ae92523d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

add-stdlib-package 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 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.

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/skills/add-stdlib-package/SKILL.md · 179 lines

How it starts

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

/add-stdlib-package — New Standard Library Package Skill

Creates a new stdlib package for the ELPS interpreter. Follows the established pattern from existing packages like libmath.

Trigger

Use when asked to add a new standard library package (e.g., file I/O, crypto, HTTP client, etc.).

Workflow

1. Plan the Package

Before writing code, define:

  • Package name (lowercase, e.g., "file", "crypto")
  • Functions to export with their signatures
  • Any global constants to expose
  • Package-level documentation

2. Create the Package Directory

Create lisp/lisplib/lib<name>/lib<name>.go:

package lib<name>

import (
	"github.com/luthersystems/elps/lisp"
	"github.com/luthersystems/elps/lisp/lisplib/internal/libutil"
)

// DefaultPackageName is the package name used by LoadPackage.
const DefaultPackageName = "<name>"

// LoadPackage adds the <name> package to env.
func LoadPackage(env *lisp.LEnv) *lisp.LVal {
	prevPkg := env.Runtime.Package.Name
	defer env.InPackage(lisp.Symbol(prevPkg))
	name := lisp.Symbol(DefaultPackageName)

	e := env.DefinePackage(name)
	if !e.IsNil() {
		return e
	}

	e = env.InPackage(name)
	if !e.IsNil() {
		return e
	}

	env.SetPackageDoc(`One-line description of the package.

Detailed description of what the package provides.`)

	// Optional: global constants
	// env.PutGlobal(lisp.Symbol("my-const"), lisp.Int(42))
	// env.SetSymbolDoc("my-const", "Description of the constant.")
	// env.Runtime.Package.Exports("my-const")

	for _, fn := range builtins {
		env.AddBuiltins(true, fn)
	}

	return lisp.Nil()
}

//elpsvet:allow package builtin table; formals are sealed by libutil at construction and shared via registrationFormals (lisp.LEnv.AddBuiltins)
var builtins = []*libutil.Builtin{
	libutil.FunctionDoc("my-func",
		lisp.Formals("arg1", "arg2"),
		builtinMyFunc,
		`Description of what my-func does.

Returns the result of ...`),
}

func builtinMyFunc(env *lisp.LEnv, args *lisp.LVal) *lisp.LVal {
	arg1 := args.Cells[0]
	arg2 := args.Cells[1]
	// Implementation
	_ = arg1
	_ = arg2
	return lisp.Nil()
}

Read the full file on GitHub · 179 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 · 179 lines · 0 tokens per session scan A 993ae92523d4

Subscribe to this mod's changes

add-stdlib-package is a skill published in the GitHub repository luthersystems/elps (36 stars, last pushed today), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 1,658 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-10-26.