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/kissrosecicd-hub/agents-evolution/engineering-principlesnpx skills add kissrosecicd-hub/agents-evolution --skill engineering-principlesgit clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolutionWrote 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/kissrosecicd-hub/agents-evolution/engineering-principles)<a href="https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/engineering-principles"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/engineering-principles.svg" alt="Measured on agentmods" 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.00139 | $0.03160 |
| Opus 5 | $0.00069 | $0.01580 |
| Sonnet 5 | $0.00028 | $0.00632 |
| Haiku 4.5 | $0.00014 | $0.00316 |
Grade A, and why
engineering-principles 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 6d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Principles — Pragmatic Balance
Priority (when in conflict)
- Работает → решает задачу пользователя
- Просто (KISS) → простейшее рабочее решение, можно понять и поддерживать
- Не усложняй заранее (YAGNI) → сначала работающий простой код, не усложнять заранее
- Убери настоящий дубль (DRY) → только когда реально нужно (3+ места), настоящая одинаковая логика
- SOLID → когда система уже растёт; маленький скрипт ≠ нужна абстракция
Что даёт каждый принцип (цель, не догма)
| Принцип | Зачем | Стоп-сигнал |
|---|---|---|
| SRP — одна ответственность | Меняешь одно → не ломает другое | Функция > 40 строк или 3+ причин менять → раздели |
| OCP — расширяй, не меняй | Новая фича → старое работает | Не создавай абстракции "на будущее" (см. YAGNI) |
| LSP — замена без сюрпризов | Подставил реализацию → работает | instanceof, if type → плохой дизайн, переделай |
| ISP — минимум зависимостей | Не тяни лишнее | Интерфейс > 5 методов → разбей |
| DIP — завись от абстракций | Меняешь деталь → бизнес-логика не знает | Не абстрагируй то что не будет меняться |
| KISS — простота | Код понятен с первого чтения | if/else на 3 ветки ≠ нужна фабрика |
| DRY — без дублирования | Баг в одном месте → починил везде | Похожий код, разная логика → НЕ трогай |
| YAGNI — фокус | Не тратишь время на ненужное | "Конфиг на будущее", "generic для всего" → стоп |
Product-first Checks
Перед финальной реализацией спроси:
- Какую видимую пользователю проблему это решает?
- Как пользователь поймёт что это сработало?
- Что сломается если входные данные, сеть, зависимость или данные — плохие?
- Можно ли это наблюдать, тестировать, откатить, объяснить?
- Это простейший код который оставляет будущие изменения продукта дешёвыми?
Product Engineering Priorities
- Correct user outcome — правильный результат для пользователя
- Clear surfaced behavior — ясные API/UI/контракты/ошибки
- Safe changeability — безопасно менять
- Operational visibility — можно наблюдать и дебажить
- Code elegance — красота кода (последний приоритет)
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.
- 6d ago First seen · 292 lines · 139 tokens per session scan A e9956e15078d
engineering-principles is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 4mo ago), licensed MIT. It adds 139 tokens to every session and 3,160 once invoked, about $0.0007 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…