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 rodlunt/engineering-audit --skill auditgit clone --depth 1 https://github.com/rodlunt/engineering-auditWrote 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/rodlunt/engineering-audit/audit)<a href="https://agentmods.dev/skills/rodlunt/engineering-audit/audit"><img src="https://agentmods.dev/badge/skills/rodlunt/engineering-audit/audit/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/rodlunt/engineering-audit/audit"><img src="https://agentmods.dev/badge/skills/rodlunt/engineering-audit/audit.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.00057 | $0.00965 |
| Opus 5.5 | $0.00023 | $0.00386 |
| Sonnet 5.5 | $0.00011 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
audit scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
server with `curl`, and do not try to open the browser yourself. Calling `get_config` while its How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering practice audit
Runs a full engineering-practice audit of the current repository via the engineering-audit
MCP server, and produces a self-contained HTML report.
The full, assistant-neutral procedure lives in this tool's own AUDIT.md (in the
engineering-audit repository this server was installed from). Follow that document as the
source of truth. The summary below exists so you do not have to fetch it before starting, but
if the two ever disagree, AUDIT.md wins.
Flow (summary)
- Gather run metadata: repository name,
git rev-parse HEAD, your own assistant/model identity, an ISO 8601 started timestamp, and the host environment (see below). - Call
begin_runwith that metadata andoutput_dirset to<repo>/audit-output/. Passenvironmentwith exactly these keys, omitting any you cannot determine:os(read from the machine, e.g.uname -srorsw_vers),host_cli("claude-code") andhost_cli_version(claude --version). Any other key is refused: seeAUDIT.mdstep 1 for why the set is closed. - Call
start_config.- Preset mode (
ENGINEERING_AUDIT_CONFIGenv var set): the config is already loaded, skip to step 4. - Interactive mode: the response has a
url. Show it to the user as a clickable line (do not open it yourself, and do not try to fetch or wait on it via Bash) and ask them to choose domains there. Then callget_configin a loop: while its response'sstatusis"waiting", call it again. Go to step 4 only once the status is"configured". - If
get_configraises, the run's overall waiting deadline has expired. Tell the user plainly that the audit is waiting on them and stop. Do not proceed with a guessed domain selection. Callget_configagain, with a largertimeout_s, once they confirm.
- Preset mode (
- For each selected domain id: call
get_domain, read the full rule text, sweep the repository giving every rule an honest verdict (pass,finding, ornot-applicableorcould-not-evaluatewith a reason: never a guessedpass), then callrecord_domain_result. If it rejects the payload as incomplete, the error lists the missing rule ids; fix and resubmit. Write every finding and issue body terse, in three parts and nothing else: the issue, why it matters, suggested fix (one or two sentences each). - Call
run_statusand confirm nothing is missing. - Call
render_reportwith a finished timestamp. Tell the user wherereport.htmllanded and give a one-line findings summary.
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 · 60 lines · 57 tokens per session scan A 7e51202a8c06
audit is a skill published in the GitHub repository rodlunt/engineering-audit (1 stars, last pushed 7d ago), licensed Apache-2.0. It adds 57 tokens to every session and 965 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
software-code-review
Evaluate source code for correctness, quality, security, style conformance, and maintainability, producing a structured review report with findings and recommendations. Use when the user wants to review, critique, audit, evaluate, or inspect source code — checking for bugs, logic errors, unhandled error paths…
plan-eng-review
Engineering plan review. Reviews a plan document for architecture, code quality, test coverage, and performance before implementation begins. Produces a coverage diagram, failure modes map, and parallelization strategy. Use when asked to "review this plan", "eng review", or "architecture review".
review
Pre-merge code review — the single canonical review of a change before it lands. Covers BOTH diff safety/structure (SQL safety, LLM trust-boundary violations, conditional side effects) AND engineering quality (architecture fit, edge cases, test coverage, performance). Use when asked to "review this PR", "code review"…
craft-audit
The front door to the craft skills — a whole-project production-readiness orchestrator that drives the ten per-domain craft skills (ux, frontend, backend, db, security, infra, observability, testing, lint, ai) instead of auditing one surface at a time. It discovers the project's shape, plans an audit per surface, and…
craft-backend
The Craftsman standard for building and reviewing backend code — API routes, request validation, the authentication boundary, service/business logic, error handling, route rate-limit middleware, third-party integrations, and background jobs. Use this WHENEVER the work touches the server side: adding or reviewing a…
codemap
Generate and incrementally maintain an interactive architecture map plus a per-module code-quality audit (health scores 0-100, smell findings, lines-of-code, and a clickable dependency graph) for any codebase. Use when the user wants to visualize a project's functional modules, audit or score code quality, check…