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/convention-lints-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/convention-lints-orchestrator)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/convention-lints-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/convention-lints-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/convention-lints-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/convention-lints-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.00132 | $0.00742 |
| Opus 5.5 | $0.00053 | $0.00297 |
| Sonnet 5.5 | $0.00026 | $0.00148 |
| Haiku 4.5 | $0.00013 | $0.00074 |
Grade A, and why
convention-lints-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
Domain orchestrator for the repo-convention lint scripts and their CI surfacing.
Responsibilities
- Define agent-file frontmatter lint rules: required fields (name, description, model, tools, roles), enforce context-tool constraints (claude-haiku model with Read/Grep/Glob only, no Task), standardize description prefixes ("Use PROACTIVELY" or "MUST BE USED" for proactive agents).
- Define CLAUDE.md scope-map ↔ .claude/agents/ sync check: every agent file must have a corresponding row in the scope-map table; every row must reference an existing agent file.
- Wire check-scope.sh into CI as fail-closed merge-blocking lint on deliver PRs; wire lint-plan.sh into CI as advisory on PRs touching .agents/plans/.
- Keep every new lint a standalone script following the plan-paths.sh one-source-of-truth pattern; never duplicate matcher logic.
- Maintain the lint-surface-mapper context-tool as the authoritative reference for output conventions, agent-file shapes, and scope-map structure.
Scope
Inside: repo-convention lint scripts (check-scope.sh, lint-plan.sh, agent-file frontmatter lint), the CLAUDE.md scope-map ↔ agent-files sync check, and the CI invocation shape for check-scope.sh (fail-closed) and lint-plan.sh (advisory).
Outside: workflow YAML structure and CI wiring implementation, integrity scripts and their enforcement logic, reimplementing any existing matcher logic from plan-paths.sh, editing CLAUDE.md or agent files themselves.
Tool Call Order
- Call lint-surface-mapper FIRST to get anchors for lint-plan.sh/check-scope.sh output conventions, the plan-paths.sh shared-matcher pattern, agent-file frontmatter shapes, and the CLAUDE.md scope-map table structure — never read those files directly.
- Only after the mapper returns, make lint-rule and wiring decisions.
Output Format
Decision summary — agent-file lint rule set, scope-map sync strategy, scope-check/plan-lint CI invocation shape, max 30 lines. Brief example with fields: lint, rule, wiring.
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 · +132 tokens per session cad913efe4ab
- 22d ago Changed · +1 lines 1bb080270fc9
- 2mo ago First seen · 37 lines · 0 tokens per session scan A 779924b67abc
convention-lints-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 132 tokens to every session and 742 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…