Borrowing it
Nothing to install: this file belongs to kissrosecicd-hub/agents-evolution. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kissrosecicd-hub/agents-evolution/main/.agents/skills/engineering-principles/SKILL.mdgit 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/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/kissrosecicd-hub/agents-evolution/engineering-principles"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/engineering-principles.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.00139 | $0.03160 |
| Opus 5.5 | $0.00056 | $0.01264 |
| Sonnet 5.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 1mo 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.
- 1mo 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 6mo ago), licensed MIT. It adds 139 tokens to every session and 3,160 once invoked, about $0.0006 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.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…