tools-registry-context SKILL.md skillA
tools-registry-context from superdesigndev/treg is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add superdesigndev/treg/tools-registry-context@git:20260928.ce916f2Pins git:20260928.ce916f2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- superdesigndev/treg
- Path
.agents/skills/tools-registry-context/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260928.ce916f2, committed Sep 28, 2026
- First version recorded
- Jul 22, 2026
- Size
- 4,212 bytes
- Repository stars
- 7,162
- License
- a license file GitHub does not identify
tools-registry context + doc upkeep. Use to warm up a fresh session (orient on the architecture + recent commits) or when working on tools-registry — changing code, rules, content, data, or process (proxy · auth/secrets · API · CLI · the registry skill) — loads the relevant fragment(s) from docs/context so you act with accurate, cited context. Accepts an optional focus query (e.g. `/tools-registry-context <area>`). Also runs `/tools-registry-context sync` to update the doc fragments after…
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
# tools-registry-context — load the right design fragment, keep docs honest tools-registry's design docs are **fragments** under `docs/context/` (one per subsystem), each declaring the source files it covers in frontmatter. [`MAP.md`](MAP.md) (next to this file) is the generated reverse index: **source file → the fragment that documents it.** This skill has two modes. ## Mode A — LOAD context (default). Adapt to *when* you're called: **Cold start (a fresh session, little/no prior context) → warm up.** Read [`docs/context/README.md`](../../../docs/context/README.md) (the index), then the fragments that matter (the `foundation`-style overview fragments plus whichever subsystems the query or repo state points at). Run `git log --oneline -15` and `git status` to catch recent commits + uncommitted work. Then give a short orientation — what tools-registry is, the subsystems in play, what changed recently — and say you're ready. **Mid-chat (a task/topic is already in play) → stay targeted.** Map the artifacts/topic at hand via [`MAP.md`](MAP.md)'s "Source file → fragment(s)" table, read **just** those fragment(s), and proceed. Don't re-warm the whole tree. …
Read the whole file at its exact version.
How to install
mdr add superdesigndev/treg/tools-registry-context@sha256:ffe36950b90a0337The line at the top of this page pins the label git:20260928.ce916f2, 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_jlgyjtly6pbhmzw6)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 22, 2026 and Sep 28, 2026, about one every 68 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260928.ce916f2 latest | 2026-09-28 | ce916f2 | 4,212 B | A | view · diff |
| git:20260722.433207b | 2026-07-22 | 433207b | 4,119 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 (4212 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
superdesigndev/treg · 7,162 stars · license a license file GitHub does not identify · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jlgyjtly6pbhmzw6 GET https://markdownregistry.com/api/v1/resolve?ref=superdesigndev/treg/tools-registry-context GET https://markdownregistry.com/api/v1/blob/ffe36950b90a0337b1cdddd8b5ef5d75580dc7a982ee84781b2798e852fc33da
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.