audit-retention SKILL.md skillA
audit-retention 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-retention@git:20261014.62aa70ePins git:20261014.62aa70e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- baristaze/swe_guidelines
- Path
scaffold/acme_root/.agents/skills/audit-retention/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.62aa70e, committed Oct 14, 2026
- First version recorded
- Sep 29, 2026
- Size
- 9,151 bytes
- Repository stars
- 94
- License
- MIT
Audit which stores grow without bound and what trims them: every table of every role, with what writes it, when a row is stale, the purge that deletes it, its retention, and whether that purge is batched and indexed; then the stores outside the database (log groups, buckets, queues, the cache). Measures the purges on a database of its own, reads staging's retention settings read-only, and writes a report with verdicts and proposed tickets. 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-retention Which tables grow for ever, which purge trims each one, and whether that purge still works when the table is large. The answer comes from the code, checked against plans on a seeded database of the run's own, and against the retention settings staging actually runs with. Read `../_shared/ops-preamble.md`, a path from this skill's folder, before the first step: the profiles, the account check, and the env file are there. ## Input `[--env local|staging|production] [--scale <n>]` `--env` is where the stores outside the database are read: `staging` by default, `local` to read none and say so. `--scale` is the seed's, `1` by default (5,000 people with a personal org each, a team org of 200 members, a million change events); `0.01` is a quick run with the same shape, whose plans prove the wiring: a sequential scan on a small table is the planner's choice, and a quick run's plan findings say "verify at scale 1". The audit reads and runs the checkout, tools and code alike; to audit another commit, run it from a checkout of that commit that has `ops/audit/`. Every command runs from the repository root. ## Role and credential …
Read the whole file at its exact version.
How to install
mdr add baristaze/swe_guidelines/audit-retention@sha256:55afcef7fc18dddeThe line at the top of this page pins the label git:20261014.62aa70e, 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_vhp5rnjppltdmjfe)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 29, 2026 and Oct 14, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.62aa70e latest | 2026-10-14 | 62aa70e | 9,151 B | A | view · diff |
| git:20260929.3422014 | 2026-09-29 | 3422014 | 9,139 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9151 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
- pass: No script tag
Source
baristaze/swe_guidelines · 94 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vhp5rnjppltdmjfe GET https://markdownregistry.com/api/v1/resolve?ref=baristaze/swe_guidelines/audit-retention GET https://markdownregistry.com/api/v1/blob/55afcef7fc18dddefefe6cac4e8a91966211c0179235a9b8d9e4c36f4065fda1
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.