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 skills/vmkteam/claude-plugins/philosophynpx skills add vmkteam/claude-plugins --skill philosophygit clone --depth 1 https://github.com/vmkteam/claude-pluginsWhat 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.00058 | $0.01472 |
| Opus 5 | $0.00029 | $0.00736 |
| Sonnet 5 | $0.00012 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
philosophy 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Philosophy — манифест vmkteam
Принципы разработки vmkteam. Источник: https://vmkteam.dev
Код
- Пиши простой код. Думай о том, кто будет его читать через год
- Кодогенерация лучше ручного кода. Меньше ручного кода — меньше багов
- Не используй интерфейсы без необходимости. Конкретные типы понятнее
- Каждый слой имеет свои модели. Конвертеры между слоями обязательны
- Три строки простого кода лучше одной умной абстракции
Go idioms we follow
Конкретные правила, которых придерживаемся на всех слоях. Большинство — mainstream Go, часть — vmkteam-специфика (явно помечено).
Базовые
context.Context— всегда первый аргумент (после receiver), никогда не в структурахerror— последний возврат. Ошибки не теряются- Обёртывание:
fmt.Errorf("context: %w", err). Проверка:errors.Is/errors.As. Свои типы ошибок — через структуру с методомError(), а не sentinel string deferдля ресурсов сразу после захвата.defer rows.Close(),defer mu.Unlock()- Zero-value ready типы — структура должна быть валидна без конструктора, когда это возможно
Типы и пакеты
- "Accept interfaces, return structs" — принимающие функции/методы работают с интерфейсами, фабрики возвращают конкретные типы
- Интерфейсы объявляются на стороне потребителя, не провайдера
- Короткие имена пакетов, одно слово. Никаких
util,common,helpers - Экспорт по необходимости — начинай с lowercase, поднимай регистр когда появляется реальный внешний потребитель
Конкурентность
- Не запускай горутины без способа их остановить.
ctx+errgroup— базовый паттерн - Каналы для сигналинга, мьютексы для разделяемого состояния — не наоборот
- Background-процессоры — метод
Run(ctx) error, возврат приctx.Done()(см. /gold-arch)
Именование
- Getters без префикса
Get:user.Name(), неuser.GetName() - Аббревиатуры в одном регистре:
userID,HTTPServer,URL - Переменная цикла —
i,u(короткое), параметр функции — длиннее и содержательнее
Производительность
- Не оптимизируй без бенчмарка.
testing.B+go test -bench pprofчерез /appkit когда нужно искать узкие места на живом сервисе
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.
- 2d ago First seen · 106 lines · 58 tokens per session scan A 86e2188d7a9f
philosophy is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 1,472 once invoked, about $0.0003 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.
Other skills, from other repositories
layered-architecture-types
Enforce primitive-at-edges / strong-types-in-Business layering and the toBus/fromBusResponse/toDB converter pattern. Use when writing, editing, or auditing Go files under app/, business/domain/, or .../stores/db.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-observability
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for…
golang-data-structures
Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing…
golang-dependency-management
Dependency management for Golang projects — go.mod and go.sum, go get install and upgrade flows, Minimal Version Selection, conflict resolution with replace/exclude/retract, govulncheck scanning of the module tree, outdated dependency and binary size auditing, vendoring, tool directives, and go.work workspaces. Use…
golang-spf13-viper
Golang configuration library using spf13/viper — layered precedence (flag > env > file > KV > default), BindPFlag/BindPFlags, SetEnvPrefix + SetEnvKeyReplacer + AutomaticEnv, ReadInConfig + ConfigFileNotFoundError, Unmarshal + mapstructure struct tags, Sub for sub-trees, WatchConfig + OnConfigChange for hot reload…