standing-rules-database-skill SKILL.md skillA

standing-rules-database-skill from nmbr5sgit/standing-rules-database-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add nmbr5sgit/standing-rules-database-skill/standing-rules-database-skill@v1.0.0

Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
nmbr5sgit/standing-rules-database-skill
Path
SKILL.md
Versions recorded
5
Latest version
v1.0.0, committed Nov 4, 2026
First version recorded
Oct 31, 2026
Size
5,545 bytes
Repository stars
3
License
MIT

Agent standing rules database: unlimited rules, bounded context — loads only rules matching each task.

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

# Standing Rules Database

A growing database of standing rules, fetched per-job instead of always-injected, to save context. **SQLite (`rules.db`) is the authoritative store; `references/*.md` are generated views.** Consult BEFORE starting any task; load only the rules whose triggers match the job.

## When to Use
Before starting ANY task: run the query, then apply only the matching rules. Consultation is mandatory pre-work, not optional: read-only rule lookups before design/debug/edit.

## How to apply (DB-first)
1. Identify the job's task domain AND its output type (does text leave this chat?).
2. Query: `python scripts/rules_db.py query --match "<domain keywords> <output-type keywords>"` — returns tier-1 mandatory rules (always) plus keyword-matched tier-2 rules with IDs and priorities. Facts: `... facts --domain X`.
3. Apply the returned rules. Log consults that mattered: `... log --task "..." --rule-ids "SR-x,SR-y" --method keyword --reason "..."`.
4. After any DB change, regenerate views: `... export-md` (markdown files are views, never edited by hand).
5. New standing rules go into the DB via the write gate below — never into always-injected memory unless tier-1.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add nmbr5sgit/standing-rules-database-skill/standing-rules-database-skill@sha256:4bd30e4832f83c10

The line at the top of this page pins the label v1.0.0, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_7q3rft6b5l4zcjxp.svg)](https://markdownregistry.com/a/art_7q3rft6b5l4zcjxp)

0 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Oct 31, 2026 and Nov 4, 2026, about one every day.

versioncommittedcommitsizeaudit
v1.0.0 latest2026-11-04 49ee542 5,545 BA view · diff
v1.0.02026-11-04 60ed7ae 5,408 BA view · diff
v1.0.02026-11-04 72d098a 5,200 BA view · diff
v1.0.02026-10-31 a5d283c 4,892 BA view · diff
v1.0.02026-10-31 bae199b 4,846 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (5545 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

GitHub

nmbr5sgit/standing-rules-database-skill · 3 stars · license MIT · pushed 2026-11-07 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_7q3rft6b5l4zcjxp
GET https://markdownregistry.com/api/v1/resolve?ref=nmbr5sgit/standing-rules-database-skill/standing-rules-database-skill
GET https://markdownregistry.com/api/v1/blob/4bd30e4832f83c102fc7ca51e2b92f7f4a50ede6312110576e9a010a4534bf0f

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.

Browse by kind, by grade A, or by owner.