hm-engineer

hm-engineer is a skill for Claude Code, Codex from rodrigohighermind/highermind-code-skills. It costs 107 tokens per session (2,744 once invoked), scanned A, original, MIT.

A senior-level code review checklist for checking a large codebase before release. It examines structure, security, reliability, performance, cost, and data handling.

In plain words
What is it for?
Use it to audit code before shipping, focusing on security practices, infrastructure, error handling, input validation, performance, and resilience.
Why use it?
It helps find serious problems that style checks and basic linting may miss, such as untyped data, exposed secrets, unsafe database queries, or unhandled background tasks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Install

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.

agentmods
npx agentmods add skills/rodrigohighermind/highermind-code-skills/hm-engineer
Any agent
npx skills add rodrigohighermind/highermind-code-skills --skill hm-engineer
Clone the repo
git clone --depth 1 https://github.com/rodrigohighermind/highermind-code-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for hm-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/rodrigohighermind/highermind-code-skills/hm-engineer.svg)](https://agentmods.dev/skills/rodrigohighermind/highermind-code-skills/hm-engineer)
Your own site
<a href="https://agentmods.dev/skills/rodrigohighermind/highermind-code-skills/hm-engineer"><img src="https://agentmods.dev/badge/skills/rodrigohighermind/highermind-code-skills/hm-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,744 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00107 $0.02744
Opus 5 $0.00053 $0.01372
Sonnet 5 $0.00021 $0.00549
Haiku 4.5 $0.00011 $0.00274

Measured 6d ago against content hash 3b7aae6db9bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

hm-engineer 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.

hm-engineer/SKILL.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/hm-engineer — Validação de Código (v3)

Você está agora em modo engineer. Seu trabalho e validar que o código é world-class em todas as camadas. Não estilo. Não lint. Estrutura, segurança, resiliencia, performance e custo.

Princípio central

Se você estivesse vendendo esse software e o comprador contratasse os melhores engenheiros do mundo pra auditar o codebase, eles não encontrariam nada pra reclamar. Essa é a barra.

Padrão senior — inegociável

Antes de qualquer auditoria, o código DEVE atender o baseline de engenheiro senior:

  • Zero bare except Exception — todo catch tem tipo especifico e contexto
  • Zero any types — tudo tipado, sem escape hatches
  • Zero fire-and-forget sem handler — toda task async tem error handling
  • Zero secrets hardcoded — nem em dev, nem em "e só teste"
  • Zero queries sem limit — toda query ao banco tem paginacao ou limite explícito
  • Zero endpoints sem validação de input — toda boundary valida dados
  • Zero prints em produção — logging estruturado com níveis corretos
  • Zero singletons stale — credenciais ou config recarregadas em runtime via factory, não module-load
  • Zero JSON.parse + cast sem validação — payload externo passa por schema (Zod, Pydantic) antes do cast
  • Zero history unbounded em LLM — toda conversa tem sliding window com limite explícito de turns

Se qualquer um desses existe, é finding CRÍTICO automático.

O que você audita

Segurança — Aplicação (OWASP Top 10)

Esta seção é a PRIMEIRA a ser auditada. Sempre.

# Categoria OWASP O que checar
A01 Broken Access Control Toda rota protegida tem auth+authz? RBAC/ABAC enforced? Sem IDOR?
A02 Cryptographic Failures Secrets em env vars (nunca hardcoded)? Hashing com bcrypt/argon2? JWT com algoritmo seguro?
A03 Injection SQL via ORM parameterizado? XSS sanitizado? Command injection impossível?
A04 Insecure Design Trust boundaries definidas? Rate limiting em endpoints públicos? Input validation em toda boundary?
A05 Security Misconfiguration CORS restrito (nunca * em prod)? Debug desabilitado em prod? Headers de segurança?
A06 Vulnerable Components Dependências com CVEs conhecidas? Lock files commitados? Audit limpo?
A07 Auth Failures Brute force protegido? Session timeout? MFA quando aplicavel? Password policy?
A08 Data Integrity Inputs validados antes de deserializar? Sem eval/exec de dados externos?
A09 Logging Failures Eventos de segurança logados? Sem secrets nos logs? Audit trail?
A10 SSRF Requests a URLs externas validadas? Sem user input em URLs internas?

Read the full file on GitHub · 190 lines

Changes

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.

  1. 6d ago First seen · 190 lines · 107 tokens per session scan A 3b7aae6db9bb

Subscribe to this mod's changes

hm-engineer is a skill published in the GitHub repository rodrigohighermind/highermind-code-skills (192 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 2,744 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens