audit-database-calls SKILL.md skillB
audit-database-calls from baristaze/swe_guidelines is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add baristaze/swe_guidelines/audit-database-calls@git:20261014.7748a1fPins git:20261014.7748a1f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- baristaze/swe_guidelines
- Path
scaffold/acme_root/.agents/skills/audit-database-calls/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261014.7748a1f, committed Oct 14, 2026
- First version recorded
- Sep 29, 2026
- Size
- 9,866 bytes
- Repository stars
- 94
- License
- MIT
Audit how many database calls each endpoint and each worker flow makes, at its least and at its most: round trips, transactions, and roles, counted at the driver while the real API and worker run in one process over a database of their own. Names what grows a flow, every N+1, every read repeated within a flow, and the fixed cost of a transaction, each with its fix and effort. Never changes anything.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# audit-database-calls For every route and every worker flow: how many round trips it sends to the database, in how many transactions, on which roles, at its least and at its most, and what makes the most grow. The count is taken at the driver while the real API and worker run in one process, so it is what the code does, not what it looks like it does. ## Input `[--only <flow,...>]` The audit counts the checkout, tools and code alike; to count another commit, run it from a checkout of that commit that has `ops/audit/`. Every command runs from the repository root. `--only` runs some of the built-in flows (`sign_in`, `members`, `invitations`, `api_keys`, `switch`, `files`, `change_events`, `org_deleted`, `account_deleted`, `sweep`, `health`), such as `--only api_keys,sweep`; `seed` always runs first, and a flows file of the run's own always runs in full. ## Role and credential None, local only. The skill runs on the local stack (`make infra-up`, with `make migrate` run once), in a database it makes and drops, with the identity provider's twin in place of the provider. It holds no cloud credential and reads no environment. ## Procedure …
Read the whole file at its exact version.
How to install
mdr add baristaze/swe_guidelines/audit-database-calls@sha256:30cc5b87316dd86cThe line at the top of this page pins the label git:20261014.7748a1f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ouqx6duvnw5aiqzg)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 29, 2026 and Oct 14, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.7748a1f latest | 2026-10-14 | 7748a1f | 9,866 B | B | view · diff |
| git:20261014.62aa70e | 2026-10-14 | 62aa70e | 9,828 B | B | view · diff |
| git:20260929.0713568 | 2026-09-29 | 0713568 | 9,816 B | B | view · diff |
| git:20260929.3422014 | 2026-09-29 | 3422014 | 9,697 B | B | view |
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9866 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
baristaze/swe_guidelines · 94 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ouqx6duvnw5aiqzg GET https://markdownregistry.com/api/v1/resolve?ref=baristaze/swe_guidelines/audit-database-calls GET https://markdownregistry.com/api/v1/blob/30cc5b87316dd86c5a262d15a00730c05e74bea56521b042c1c7e71a579f271d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.