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/lootlog/monorepo/engineering-rigornpx skills add lootlog/monorepo --skill engineering-rigorgit clone --depth 1 https://github.com/lootlog/monorepoWrote 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/lootlog/monorepo/engineering-rigor)<a href="https://agentmods.dev/skills/lootlog/monorepo/engineering-rigor"><img src="https://agentmods.dev/badge/skills/lootlog/monorepo/engineering-rigor.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 | $0.00054 | $0.00325 |
| Opus 5 | $0.00027 | $0.00162 |
| Sonnet 5 | $0.00011 | $0.00065 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
engineering-rigor 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 today.
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.
What it actually says
Engineering rigor
Make the smallest complete change that reaches the intended architecture.
Shape
- Model the domain in data structures instead of scattered conditions.
- Concentrate parsing, validation, and framework adaptation at system boundaries.
- Prefer deep modules with small interfaces and low reader load.
- Remove dead code and redundant layers before adding abstractions.
- Redesign from the requirement as a first-class constraint instead of bolting on exceptions.
Change
- Migrate every caller and delete the legacy internal API in the same change.
- For internal APIs, migrate callers instead of adding compatibility layers unless the user requests them. Preserve deployed and persisted contracts required by
AGENTS.md, including coordinated rollout where needed. - Delete re-export-only wrappers and import from the owning module.
- Separate concurrent writers before adding locks. When shared state is necessary, make operations idempotent across retries and partial failures.
- Break wide work into verifiable units. Keep every intermediate commit or phase coherent.
Prove
- Reproduce defects before fixing them when practical.
- Verify the real artifact, not only a proxy such as compilation.
- Inspect the diff and generated output.
- Run targeted tests, typecheck, lint, and broader checks in proportion to risk.
Use blast-radius when the main risk lies outside the edited symbols.
What ships with it
1 file 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.
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.
- today Changed · -1 lines 6b0d88b0b019
- 5d ago First seen · 35 lines · 54 tokens per session scan A 61c9e346db19
engineering-rigor is a skill published in the GitHub repository lootlog/monorepo (10 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 325 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
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…