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 skills add vmkteam/claude-plugins --skill philosophygit clone --depth 1 https://github.com/vmkteam/claude-pluginsWrote 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/skills/vmkteam/claude-plugins/philosophy)<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/philosophy"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/philosophy/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.
<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/philosophy"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/philosophy.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00058 | $0.01529 |
| Opus 5.5 | $0.00023 | $0.00612 |
| Sonnet 5.5 | $0.00012 | $0.00306 |
| Haiku 4.5 | $0.00006 | $0.00153 |
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 23d 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 — 107 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, никогда не сравнивайerr.Error()со строкой. Ошибка-значение — sentinel-переменная (var ErrNotFound = ...), ошибка с данными — тип с методомError() 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(короткое), параметр функции — длиннее и содержательнее
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.
- 23d ago Changed · +1 lines 3731e61a3821
- 1mo 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 6d ago), licensed MIT. It adds 58 tokens to every session and 1,529 once invoked, about $0.0002 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-31.
Other skills, from other repositories
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
ax-go-agent-optimize
Use when writing Go code with github.com/ax-llm/ax/packages/go for agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA.
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-uber-fx
Golang application framework using uber-go/fx — fx.New, fx.Provide, fx.Invoke, fx.Module, fx.Lifecycle hooks, fx.Annotate (name/group/As), fx.Decorate, fx.Supply, fx.Replace, fx.WithLogger, and signal-aware Run(). Apply when using or adopting uber-go/fx, when the codebase imports go.uber.org/fx, or when wiring…
golang-samber-oops
Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports…