A set of coding rules for Python, Rust, TypeScript, and Go files. It favours strict type checking, modern development tools, and turning parsed data into well-defined types before using it.

Writing, reviewing, and changing files in these four programming languages with the listed toolchains and practices.

It gives code changes a consistent standard for type safety, formatting, linting, and error handling.

programming — Skill for Claude Code and Codex by daeryundf2-prog

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.

Any agent

npx skills add daeryundf2-prog/LAZYANTIGRAVITY --skill programming

Clone the repo

git clone --depth 1 https://github.com/daeryundf2-prog/LAZYANTIGRAVITY

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/daeryundf2-prog/lazyantigravity/programming/github.svg)](https://agentmods.dev/skills/daeryundf2-prog/lazyantigravity/programming)

Your own site

<a href="https://agentmods.dev/skills/daeryundf2-prog/lazyantigravity/programming"><img src="https://agentmods.dev/badge/skills/daeryundf2-prog/lazyantigravity/programming/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/daeryundf2-prog/lazyantigravity/programming"><img src="https://agentmods.dev/badge/skills/daeryundf2-prog/lazyantigravity/programming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 261 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,798 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.

Model	Per session	Once invoked
Fable 5.1	$0.00261	$0.01798
Opus 5.5	$0.00104	$0.00719
Sonnet 5.5	$0.00052	$0.00360
Haiku 4.5	$0.00026	$0.00180

Measured 1mo ago against content hash 6cd6c8b8b621, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

programming 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 1mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/go/check-no-excuse-rules.sh, scripts/go/new-project.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

shared-skills/skills/programming/SKILL.md · 90 lines

How it starts

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

Programming

You are a senior engineer who writes Python, Rust, TypeScript, and Go with one shared discipline: Type-strict. Stack-first. Async-correct. Architecturally honest about file size (250 LOC ceiling).

This skill is an index. Detailed per-language rules live under references/. Load the language-specific reference before writing a single line of code.

PHASE 0 — LANGUAGE GATE (RUN THIS FIRST, EVERY TIME)

DO NOT WRITE OR EDIT A SINGLE LINE OF CODE BEFORE COMPLETING THIS GATE.

Identify the language from file extensions or user requests.

STOP and load the matching reference set:

File / Language	MANDATORY reading (load `view_file` on every file below)
`.py`, `.pyi`, "Python"	`references/python/README.md` + topic guides under `references/python/`
`.rs`, `Cargo.toml`, "Rust"	`references/rust/README.md` + topic guides (`unsafe` work touches `references/rust-ub/`)
`.ts`, `.tsx`, `.mts`, `.cts`, "TypeScript"	`references/typescript/README.md` + topic guides under `references/typescript/`
`.go`, `go.mod`, `go.sum`, "Go" / "Golang"	`references/go/README.md` + topic guides under `references/go/`

Apply the shared philosophy below plus the per-language iron rules.

Shared Philosophy (All Languages)

The best code is the code never written. Before writing, stop at the first rung that holds: (1) does this need to exist at all? (YAGNI) (2) does this codebase already have it? — reuse the helper or pattern, do not re-implement. (3) does the standard library do it? (4) does a native platform feature cover it? (5) does an installed dependency solve it? (6) can it be one line? (7) only then, write the minimum that works. Bug fix = root cause, not symptom; fix at the shared seam.
The type system is your proof system. Make illegal states unrepresentable. Express bugs as compile-time type errors.
Parse, don't validate. Untrusted input crosses a boundary once (Pydantic v2, serde, Zod, validator/v10). Inside the boundary, code receives typed values.
One name = one concept. Use branded types / newtypes (UserId = NewType(...), struct UserId(u64), type UserId = Brand<...>).
Exhaustive variant matching, always. Match unions/enums exhaustively with assert_never / assertNever. Never use if/elif variant chains.
Trust framework guarantees. Validate only at boundaries; avoid redundant null checks for proven non-null types.
Tests are the behavior of record, and only tests that can fail count. Read existing tests covering the area before changing code. Reproduce a bug before fixing it. The run proves the change; add a test only where the repository keeps tests for this behavior and a regression would otherwise pass unnoticed — sized like its neighbors, never restating trivial changes.

Read the full file on GitHub · 90 lines

Files

What ships with it

60 files 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.

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.

1mo ago Changed · +10 lines 6cd6c8b8b621
1mo ago First seen · 80 lines · 261 tokens per session scan A 024c9c98f11a

Subscribe to this mod's changes

programming is a skill published in the GitHub repository daeryundf2-prog/LAZYANTIGRAVITY (14 stars, last pushed 6d ago), licensed MIT. It adds 261 tokens to every session and 1,798 once invoked, about $0.0010 per session on Opus 5.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.

Languages Python TypeScript agentic-coding ai-agent automation developer-tools lazycodex

effect-v4

Write, review, or upgrade Effect v4 code in the Composio CLI, cli-keyring, and json-schema-to-effect-schema packages, all pinned exactly to [email protected] — Context.Service and explicit layers, Schema.TaggedError and typed recovery, the effect/cli command surface, and the vendored effect source oracle. Use when writing…

ComposioHQ/composio · 157 tokens

langgraph-docs

Fetches and references LangGraph Python documentation to build stateful agents, create multi-agent workflows, and implement human-in-the-loop patterns. Use when the user asks about LangGraph, graph agents, state machines, agent orchestration, LangGraph API, or needs LangGraph implementation guidance.

langchain-ai/deepagents · 62 tokens

stripe-projects

Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.

e2b-dev/E2B · 51 tokens

migrating-mastra-to-pydantic-ai

Migrate TypeScript Mastra applications to Python with Pydantic AI and, only when needed, Pydantic AI Harness. Use when source code imports @mastra/ or relies on Mastra agents, tools, workflows, memory, processors, streaming, approvals, skills, or subagents.

pydantic/pydantic-ai · 73 tokens

migrating-vercel-ai-sdk-and-eve-to-pydantic-ai

Migrate TypeScript Vercel AI SDK or Eve applications to Python with Pydantic AI and, only when needed, Pydantic AI Harness. Use when source code imports ai, @ai-sdk/, or eve, or relies on generateText, streamText, ToolLoopAgent, useChat, Eve agents, tools, skills, subagents, approvals, sessions, channels, schedules…

pydantic/pydantic-ai · 107 tokens

migrating-pi-to-pydantic-ai

Migrate TypeScript Pi coding-agent applications, extensions, or packages to Python with Pydantic AI and Pydantic AI Harness. Use when source code imports @earendil-works/pi-, calls createAgentSession, registers Pi extensions, or relies on Pi tools, hooks, skills, sessions, compaction, providers, TUI, RPC, or packages.

pydantic/pydantic-ai · 88 tokens