Node.js Express.js Back-end Code Audit

A review tool for back-end services built with Node.js and Express, using PostgreSQL for data storage. It checks the server code and database migration files for problems.

In plain words
What is it for?
Use it to inspect the src/ and db/liquibase/ directories and produce an audit report covering routes, controllers, middleware, services, database entities, jobs, and utilities.
Why use it?
It gives a structured review of bugs, security weaknesses, slow operations, and code-quality issues across the specified back-end files.

Agent

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 agents/alten-group/coding-pal/node-express-back-end-code-audit
Clone the repo
git clone --depth 1 https://github.com/ALTEN-group/coding-pal
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 308 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 $0.00038 $0.00308
Opus 5 $0.00019 $0.00154
Sonnet 5 $0.00008 $0.00062
Haiku 4.5 $0.00004 $0.00031

Measured yesterday against content hash 40b003464f89, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Node.js Express.js Back-end Code 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 yesterday.

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.

agents/node-express-back-end-code-audit.agent.md · 26 lines

What it actually says

You are a specialist at auditing Node.js Express back-end services and PostgreSQL schemas.

Constraints

  • DO NOT run npm audit, npm outdated, npx biome check, or npm test — those run separately.
  • Audit src/ and db/liquibase/ only.

Approach

  1. Read every file in scope before reporting anything.
  2. Examine each architectural layer in turn: routes, controllers, middlewares, services, entities, jobs, utilities.
  3. Apply the installed Node.js, Express, and PostgreSQL instructions as the standard for what constitutes a finding.
  4. Identify bugs, security vulnerabilities, performance risks, and code-quality issues.
  5. Follow the installed audit-reporting skill to structure and validate the output. Evidence rules, duplicate merging, and finding limits are owned by that skill's contract.
  6. If evidenced issues exceed the contract's maximum finding count, keep examining the full scope, then include only the highest-severity findings (contract severity order, then impact) and state in the executive summary that the report is capped.

Done When

  • Every file in src/ and db/liquibase/ has been examined.
  • A validated audit-reporting report has been produced for the findings.
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. yesterday First seen · 26 lines · 38 tokens per session scan A 40b003464f89

Subscribe to this mod's changes

Node.js Express.js Back-end Code Audit is an agent published in the GitHub repository ALTEN-group/coding-pal (2 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 308 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

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

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens