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 skills add baristaze/swe_guidelines --skill arch-review-omgit clone --depth 1 https://github.com/baristaze/swe_guidelinesWrote 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/skills/baristaze/swe_guidelines/arch-review-om)<a href="https://agentmods.dev/skills/baristaze/swe_guidelines/arch-review-om"><img src="https://agentmods.dev/badge/skills/baristaze/swe_guidelines/arch-review-om/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/skills/baristaze/swe_guidelines/arch-review-om"><img src="https://agentmods.dev/badge/skills/baristaze/swe_guidelines/arch-review-om.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.00047 | $0.02697 |
| Opus 5.5 | $0.00019 | $0.01079 |
| Sonnet 5.5 | $0.00009 | $0.00539 |
| Haiku 4.5 | $0.00005 | $0.00270 |
Grade A, and why
arch-review-om 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 12d 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.
This is a copy
92% identical to arch-review-{group} — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
arch-review-om
Judge the code from one perspective only: the lenses in
../../lenses/om.md. Other perspectives have their own skills; do
not borrow their rules, and do not flag anything a lens in this file
does not name. The guideline itself is at ../../architecture.md when a
lens needs its source read in full. A path that starts with ../ is
read from this skill's folder as realpath resolves it. If either file
is missing, stop and say the installation is incomplete.
This pass covers The Domain as the Source of Truth, Naming Entities, Namespaces as Swimlanes: source of truth, mixins, immutability, identifiers, namespaces, pure rules.
Input
The arguments name what to review. Read them as the first of these that matches:
- Empty: the current branch's change. The default branch is
origin/HEADwhen set, elsemain, elsemaster. The scope is every file changed since the merge base ofHEADand the default branch (git diff --name-only <base>, committed and uncommitted alike), plus every untracked file git does not ignore (git status --porcelain --untracked-files=all). When there is no merge base (no default branch, a shallow clone, or unrelated histories), the scope is the uncommitted change againstHEADplus the untracked files, and the Scope line says the merge base was not found. In a repository with no commit, it is every file not ignored, listed asalllists them. - The word
all: every file in the repository that git does not ignore, tracked or untracked (git ls-files --cached --others --exclude-standard). Expect this to take a while. - A range (
main..HEAD,main...HEAD): the files that range changes, read as they are at its end. - A commit that
git rev-parse --verify --quiet "<arg>^{commit}"resolves (a SHA, a tag, a branch): the change that commit made, against its first parent. - A path or a glob: every file under it as it is now, untracked files
included
(
git ls-files --cached --others --exclude-standard -- <path>). A path that does not exist is an error; say so and stop. A name that is both a commit and a path reads as the commit; write./<name>for the path.
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.
- 12d ago Changed · +9 lines 974db9244ceb
- 16d ago Changed · +28 lines d32b206ce1c2
- 24d ago Changed · +39 lines · -31 tokens per session 86990fc859ae
- 25d ago Changed · +37 lines 046ceb73e24d
- 26d ago First seen · 92 lines · 78 tokens per session scan A 27ed43e79c87
arch-review-om is a skill published in the GitHub repository baristaze/swe_guidelines (94 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,697 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to arch-review-{group}, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:mapping-streaming-events
Mapping the eventable points in a Lerian Go service where lib-streaming should emit past-tense, durable, tenant-scoped business events, producing a PM-validated event catalog and instrumentation-map.json for ring:instrumenting-streaming-events. Three-pass discovery (Survey, Slice, Mark) with a scope fence and delivery…