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.
git clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/commands/fmarzochi/egc/engineering-audit)<a href="https://agentmods.dev/commands/fmarzochi/egc/engineering-audit"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/engineering-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/commands/fmarzochi/egc/engineering-audit"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/engineering-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.00000 | $0.00939 |
| Opus 5 | $0.00000 | $0.00469 |
| Sonnet 5 | $0.00000 | $0.00188 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
engineering-audit 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Audit
Input: $ARGUMENTS
Runs a full engineering health assessment of the current project. Produces an Engineering Score (0–10), a ranked issue list (CRITICAL / HIGH / MEDIUM / LOW), and a concrete remediation plan.
This command NEVER modifies files. Use /engineering-fix to apply corrections after reviewing the plan.
Argument Handling
Parse $ARGUMENTS:
| Argument | Behavior |
|---|---|
--threshold <N> |
Only report issues where score < N (e.g. --threshold 7 shows scores below 7) |
--focus <dimension> |
Run only one dimension (e.g. --focus security, --focus complexity) |
--quick |
Skip slow checks (coverage, duplicate detection): fast scan only |
| blank | Full audit, all dimensions |
Execution
Step 1: Detect Project
ls package.json tsconfig.json pyproject.toml go.mod Cargo.toml 2>/dev/null
Identify: Node/TypeScript, Python, Go, Rust, or mixed. Adjust tool selection accordingly.
Step 2: Run Audit
Invoke the engineering-auditor agent with the project context and parsed arguments.
The agent will:
- Collect metrics across all 12 dimensions (or the focused dimension if
--focuswas passed) - Score each dimension 0–10
- Compute the weighted Engineering Score
- Rank all findings: CRITICAL → HIGH → MEDIUM → LOW
Step 3: Display Report
Print the full report:
═══════════════════════════════════════════════
ENGINEERING AUDIT: <project name>
<timestamp>
═══════════════════════════════════════════════
Engineering Score: X.X / 10
Maintainability X.X [████████░░]
Security X.X [█████████░]
Testing X.X [██████░░░░]
Architecture X.X [████████░░]
Documentation X.X [█████░░░░░]
Lint Health X.X [█████████░]
Type Safety X.X [████████░░]
Build Health X.X [██████████]
───────────────────────────────────────────────
CRITICAL (N)
───────────────────────────────────────────────
▸ [file:line] description
Root cause: ...
Fix: Extract Method: split into X and Y
HIGH (N)
───────────────────────────────────────────────
▸ [file:line] description
MEDIUM (N)
───────────────────────────────────────────────
▸ [file:line] description
LOW (N)
───────────────────────────────────────────────
▸ [file:line] description
───────────────────────────────────────────────
To apply fixes: /engineering-fix
───────────────────────────────────────────────
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 · 126 lines · 0 tokens per session scan A 2b5d42b8e6e4
engineering-audit is a command published in the GitHub repository Fmarzochi/EGC (49 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 939 tokens. 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-09-03.
Other commands, from other repositories
demand-discovery
Run automated niche demand discovery research across 7 data sources and 26 categories.
gaai-audit
Show workspace audit log with filters and optional JSON export.
rclone_config_dump
Dump the config file as JSON.
help
Get help with the hookify plugin.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.