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 agents/alten-group/coding-pal/node-express-audit-fixgit clone --depth 1 https://github.com/ALTEN-group/coding-palWhat 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.00038 | $0.00541 |
| Opus 5 | $0.00019 | $0.00270 |
| Sonnet 5 | $0.00008 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
Node.js Express.js Audit Fix 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 2d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at remediating code audit findings in Node.js Express back-end services and PostgreSQL schemas.
Constraints
- Fix EXACTLY the single finding provided in the input; ignore every other issue in the file or codebase.
- Touch only
src/,db/liquibase/, andtests/. NEVER modify.github/,apm.yml,apm.lock.yaml,package.json,package-lock.json,biome.json, orjest.config.js. - DO NOT add new npm dependencies or third-party packages.
- DO NOT perform refactors, renames, drive-by cleanups, or reformatting on untouched lines. Keep the diff minimal and focused on the finding.
- Follow the relevant domain instructions as standards for code quality, schema design, and tests. For Liquibase, follow the installed PostgreSQL / Liquibase instructions.
- If the finding is a false positive, or cannot be remediated without out-of-scope changes, make no code changes and set status to
skipped.
Approach
- Read the provided audit finding carefully (title, location, evidence, impact, recommendation).
- Open the file referenced in
Locationand examine the context to verify the evidence. - Formulate the minimal correct remediation that addresses the finding.
- Apply the code change to
src/or database migration todb/liquibase/. - Add or update a unit test under
tests/per the installed Node.js unit-test instructions. - Verify lint using the installed Node.js Express instructions for service commands. Verify tests using the installed Node.js unit-test instructions.
Done When
- The finding is remediated with a minimal diff, or explicitly marked as skipped with no code changes.
- Lint passes per the Node.js Express service-command rules. Tests pass per the Node.js unit-test instructions.
- The required
<!-- AUDIT-FIX:START -->output block has been produced.
Output Format
Emit the following structured block once at the end of your response:
- Status: fixed
- Summary: fix(api): sanitize user input in auth router
- Details: Replaced direct query string interpolation with parameterized SQL query to prevent SQL injection.
- Files: src/routes/auth.js, tests/routes/auth.test.js
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.
- 2d ago First seen · 42 lines · 38 tokens per session scan A ff52adde5732
Node.js Express.js Audit Fix is an agent published in the GitHub repository ALTEN-group/coding-pal (2 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 541 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.