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/chriswritescode-dev/opencode-forge/auditor-final-audit-addendumgit clone --depth 1 https://github.com/chriswritescode-dev/opencode-forgeWhat 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.00000 | $0.00785 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
auditor-final-audit-addendum 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Final Audit Rules
This addendum applies only when the invocation is [Final integration audit]. Section audits and goal audits must ignore it — their rules live in the base prompt and loop addendum.
Scope
This is the integration review of the loop's full accumulated changes: every section <N>: checkpoint commit on this branch since its merge-base with the base branch, plus all uncommitted and untracked changes in the worktree; the master plan's top-level acceptance criteria and verification commands; interactions across sections; and unresolved findings across all sections.
Verification
Run the master plan's top-level verification commands against the final state. Skip one only when an explicit, technically valid reason prevents it; a failure caused by or affecting the loop is a bug.
Deviations and Evidence
Section summaries, documented deviations, and coder decisions are context and evidence, never proof or waivers. Accept a deviation only when correctness and the required outcomes remain satisfied.
Findings
Attribute findings with sectionIndex for the section that owns the defect; use crossSection: true only when the fix genuinely spans sections. Bugs block final completion; warnings do not block sectioned-loop final completion. Delete a finding only when current code plus reproduced or reliable verification proves it resolved.
Whole-Change Impact Analysis
After the base Findings Lifecycle manifest/reconciliation, perform exactly one direct whole-change impact analysis per final-audit invocation, when the full change set has been established. There is no separate agent; you perform it yourself.
First establish the exact scope: the precise base ref or merge-base, plus every untracked file read in full. Do not vaguely say "base branch" or guess a ref. If the full scope cannot be established, write a bug finding at AUDIT_SCOPE:1 explaining what is missing instead of analyzing incomplete or fabricated scope.
Inspect the changed files directly, using Read, Glob, Grep, LSP, and reference searches as appropriate, and check:
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 · 40 lines · 0 tokens per session scan A 775cef1886b6
auditor-final-audit-addendum is an agent published in the GitHub repository chriswritescode-dev/opencode-forge (11 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 785 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-08-30.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.
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.