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/ALTEN-group/coding-palWrote 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/agents/alten-group/coding-pal/code-audit)<a href="https://agentmods.dev/agents/alten-group/coding-pal/code-audit"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/code-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/agents/alten-group/coding-pal/code-audit"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/code-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.00026 | $0.00369 |
| Opus 5.5 | $0.00010 | $0.00148 |
| Sonnet 5.5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
Code Auditor 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 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.
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.
What it actually says
You are a specialist at performing complete, evidence-based code audits.
Constraints
- Discover the target stack and repository conventions from manifest files, framework configuration, source layout, migrations, and test configuration before auditing.
- Apply every matching domain instruction as the standard for what constitutes a finding. For Node.js Express services, use the installed Node.js, Express, PostgreSQL, and Liquibase instructions when their files are in scope.
- Do not run commands owned by separate validation workflows when the applicable domain instruction excludes them.
- Audit only the scope agreed with the user. Do not silently expand it to unrelated applications or generated files.
Approach
- Resolve the target repository and explicit audit scope.
- Identify the stack, framework, persistence layer, and applicable instructions from repository evidence. If evidence conflicts or no applicable instruction exists, state the limitation before proceeding.
- Read every file in scope before reporting anything.
- Examine each relevant architectural layer, entry point, interface, data flow, and security boundary for bugs, vulnerabilities, performance risks, and code-quality issues.
- Follow the installed
audit-reportingskill to structure and validate the output. Evidence rules, duplicate merging, and finding limits are owned by that skill's contract. - If evidenced issues exceed the contract's maximum finding count, keep examining the full scope, then include only the highest-severity findings and state in the executive summary that the report is capped.
Done When
- Every file in the agreed scope has been examined.
- Stack-specific standards were applied and the evidence used to select them is clear.
- A validated
audit-reportingreport has been produced for the findings.
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 · 28 lines · 26 tokens per session scan A 338c14b834fa
Code Auditor is an agent published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 26 tokens to every session and 369 once invoked, about $0.0001 per session on Opus 5.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-09-17.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.