vaultspec-code-research SKILL.md skillA
vaultspec-code-research from nevenincs/vaultspec-core is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nevenincs/vaultspec-core/vaultspec-code-research@git:20260924.afdc9eaPins git:20260924.afdc9ea in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nevenincs/vaultspec-core
- Path
.vaultspec/skills/vaultspec-code-research/SKILL.md- Versions recorded
- 6
- Latest version
- git:20260924.afdc9ea, committed Sep 24, 2026
- First version recorded
- Jun 25, 2026
- Size
- 1,791 bytes
- Repository stars
- 2
- License
- MIT
Ground a decision or plan in how real code does it. Use when an ADR or plan needs a blueprint from this or another codebase.
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
# Code research (vaultspec-code-research)
Produces a Reference record: how a codebase (this project, a submodule, or an external
reference) implements the thing, as patterns with locators. It is an entry point
alongside `vaultspec-research`; sufficient Audit evidence can also ground an ADR. This
skill terminates within one run.
## Steps
- Discover per the `vaultspec-discovery` rule: locate code by meaning, read the
epicenter or nearest analogue whole, confirm exact symbols with grep, and list the
decisions.
- Scaffold: `vaultspec-core vault add reference --feature {feature}` (or the `create`
tool). Read `.vaultspec/templates/reference.md`; its hint blocks fix the body shape.
- Audit in this run, or dispatch the `vaultspec-reference-auditor` persona to locate and
audit the `{feature}` implementation in the named codebase; it returns findings for
you to persist. If the record exists already, update its body.
- Verify with `vaultspec-core vault check all`.
## Quality gate
- **Faithful.** Exact module and `file:line`; the reference's version or commit pinned.
- **Pattern-level.** Abstractions, boundaries, and module interactions; never pasted
implementation.
…Read the whole file at its exact version.
How to install
mdr add nevenincs/vaultspec-core/vaultspec-code-research@sha256:38b76510a2c8d37eThe line at the top of this page pins the label git:20260924.afdc9ea, 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_e7idlpo5bnbhcmsw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 25, 2026 and Sep 24, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.afdc9ea latest | 2026-09-24 | afdc9ea | 1,791 B | A | view · diff |
| git:20260909.aa89b93 | 2026-09-09 | aa89b93 | 1,996 B | A | view · diff |
| git:20260908.ce86e08 | 2026-09-08 | ce86e08 | 1,998 B | A | view · diff |
| git:20260905.f755314 | 2026-09-05 | f755314 | 1,935 B | A | view · diff |
| git:20260626.475d40c | 2026-06-26 | 475d40c | 2,955 B | A | view · diff |
| git:20260625.f1f2e07 | 2026-06-25 | f1f2e07 | 2,776 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 (1791 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
nevenincs/vaultspec-core · 2 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e7idlpo5bnbhcmsw GET https://markdownregistry.com/api/v1/resolve?ref=nevenincs/vaultspec-core/vaultspec-code-research GET https://markdownregistry.com/api/v1/blob/38b76510a2c8d37ea6caf558f7a0f3bbdd0ac5a90962dd4ff6d479003b27ef76
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.
More from nevenincs/vaultspec-core
Every file in nevenincs/vaultspec-core