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-storagegit 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-storage)<a href="https://agentmods.dev/skills/baristaze/swe_guidelines/arch-review-storage"><img src="https://agentmods.dev/badge/skills/baristaze/swe_guidelines/arch-review-storage/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-storage"><img src="https://agentmods.dev/badge/skills/baristaze/swe_guidelines/arch-review-storage.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.00038 | $0.02667 |
| Opus 5.5 | $0.00015 | $0.01067 |
| Sonnet 5.5 | $0.00008 | $0.00533 |
| Haiku 4.5 | $0.00004 | $0.00267 |
Grade A, and why
arch-review-storage 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
97% 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-storage
Judge the code from one perspective only: the lenses in
../../lenses/storage.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 Storage Layer and Identifiers: storage principles, tables, translation, roles, migrations.
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 8d62cb7cedf7
- 16d ago Changed · +28 lines d222eb0ab95f
- 24d ago Changed · +39 lines · -20 tokens per session 73f81c006456
- 25d ago Changed · +37 lines d7fb8df7409b
- 26d ago First seen · 92 lines · 58 tokens per session scan A 94dd884d1867
arch-review-storage is a skill published in the GitHub repository baristaze/swe_guidelines (94 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 2,667 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to arch-review-{group}, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
ring:mapping-service-resources
Mapping a Go service's Service -> Module -> Resource hierarchy for dispatch-layer registration: detects modules and per-module PostgreSQL/MongoDB/RabbitMQ resources, database names, and shared databases, generates MongoDB index migration pairs (.up.json/.down.json), detects existing Postgres migrations, emits an HTML…
tom-lane-perspective
A perspective skill based on research about Tom Lane, a PostgreSQL core maintainer. PostgreSQL is an open-source database; the skill applies his documented ways of thinking to project governance, patch review, and debugging decisions.
postgresql
PostgreSQL schema design, query optimization, indexing, and administration. Use when writing schemas, queries, migrations, or mentions PostgreSQL, Postgres, JSONB, partitioning, RLS, CTEs, window functions, EXPLAIN ANALYZE, or connection pooling.
sqlx-code-review
Reviews sqlx database code for compile-time query checking, connection pool management, migration patterns, and PostgreSQL-specific usage. Use when reviewing Rust code that uses sqlx, database queries, connection pools, or migrations. Covers offline mode, type mapping, and transaction patterns.
ia-postgresql
PostgreSQL schema design, query optimization, indexing, and administration. Use when working with PostgreSQL, JSONB, partitioning, RLS, CTEs, window functions, or EXPLAIN ANALYZE.
postgres-code-review
Reviews PostgreSQL code for indexing strategies, JSONB operations, connection pooling, and transaction safety. Use when reviewing SQL queries, database schemas, JSONB usage, or connection management.