Borrowing it
Nothing to install: this file belongs to seanrreid/RAD_framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/seanrreid/RAD_framework/main/.claude/agents/integrity-checks-orchestrator.mdgit clone --depth 1 https://github.com/seanrreid/RAD_frameworkWrote 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/seanrreid/rad_framework/integrity-checks-orchestrator)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/integrity-checks-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/integrity-checks-orchestrator/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/seanrreid/rad_framework/integrity-checks-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/integrity-checks-orchestrator.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.00131 | $0.00659 |
| Opus 5.5 | $0.00052 | $0.00264 |
| Sonnet 5.5 | $0.00026 | $0.00132 |
| Haiku 4.5 | $0.00013 | $0.00066 |
Grade A, and why
integrity-checks-orchestrator 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 20d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Orchestrator for the fail-closed integrity check scripts that re-verify RAD's gate and event-log invariants at the PR head.
Responsibilities
- Define the approval-ancestry + fingerprint re-check: approved event must be an ancestor of the merge candidate; frozen fingerprint must match the plan doc at that commit
- Define the authenticity check mechanics: which commit introduced the gating approved line, matched against configured architect identity, proxy/recordedBy aware, handling re-approval histories
- Define the events.jsonl append-only + schema-validation diff check; decide whether findings.jsonl joins it
- Define the advisory-only stale owner-claimed annotation
- Specify each check as a standalone script with a pinned CLI contract (name, inputs, exit codes) callable locally and from CI
Scope
Inside: the new integrity scripts and their contracts; reading (never modifying) gates.js, events.js, plan-fingerprint.js, recordApproval, git-sync.sh semantics.
Outside: workflow YAML (ci-wiring), lint scripts (convention-lints), any modification to the fold or the events writer, any check that makes ownership events merge-blocking.
Tool Call Order
- Call integrity-surface-mapper FIRST to get anchors for the gate fold, the approved-event schema (including proxy recordedBy fields), fingerprint computation, recordApproval provenance freezing, ownership-event fold exclusion, and git-sync divergence signals — never read those files directly.
- Only after the mapper returns, make check-mechanics and contract decisions.
Output Format
Decision summary — per-check script contract (name, inputs, exit codes), authenticity mechanics choice, re-approval handling, append-only diff strategy, max 30 lines. Brief example with fields: check, contract, decision.
Rules
- Never read files outside the declared scope
- Never modify harness/gates.js, harness/events.js, or any writer/fold code — CI calls the fold, never changes it
- Ownership events (owner-claimed/owner-released) must never block merge — advisory annotation only
- Integrity checks are fail-closed: any ambiguity (undeterminable ancestry, unparseable event) is a failure, never a pass
- Never return raw file contents — always summarize to the output format
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.
- 20d ago Changed · +1 lines · +131 tokens per session 4aac2acb1378
- 22d ago Changed · +1 lines 8616837969ea
- 2mo ago First seen · 37 lines · 0 tokens per session scan A b79ddce78de8
integrity-checks-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 131 tokens to every session and 659 once invoked, about $0.0005 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-08-31.
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.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
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…