toolcraft skillA
toolcraft is agent-read markdown (skill) from llopresto87/cypress: Doctrine (kernel §3.8) — when an operation will recur across independent sessions, the unit of work is a durable, tested, cataloged tool, not a throwaway script. Defines what counts as a durable tool, what stays disposable, the procedure sibling (a project skill), and the fail-closed rule that a task is incomplete until a durable tool is cataloged or recorded absent. AUTHORING a tool is agent.tool-smith; CATALOGING one happens inside the single canonize close-out spawn. This node is the rule bot.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# toolcraft — the durable-tool doctrine This node owns **the toolcraft rule** (kernel §3.8) — durable tools compound; throwaway scripts are rework. When an operation will recur across independent sessions, the unit of work is a **durable, tested tool** with a stable interface — designed so at plan time, named in `tools_built` on every handback, and cataloged in `docs/graph/tools/` by the librarian inside the close-out spawn. Genuine one-offs and throwaway prototypes stay disposable. A task is **not complete** until any durable tool is cataloged or explicitly recorded absent. Work generates capabilities, not only knowledge. A task needs an operation performed — seed a fixture, migrate a schema, probe an endpoint, regenerate a client — and an agent writes code to do it. If that code dies with the session, the next task that needs the same operation writes it again, slightly differently, with a fresh chance to get it wrong. Toolcraft is the doctrine that keeps a capability once it is worth keeping. **This node is the rule, not either half of the work.** Three things used to sit in one file and are now separate, because they happen at different times and are …
Read the whole file at its exact version.
How to install
mdr add llopresto87/cypress/toolcraft@git:20260915.df30567mdr add llopresto87/cypress/toolcraft@sha256:6587bf072243a87aPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_q7zcg7dyupnocuag)
1 badge views in 30 days
Versions
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 (7580 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
llopresto87/cypress · 43 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q7zcg7dyupnocuag GET https://markdownregistry.com/api/v1/resolve?ref=llopresto87/cypress/toolcraft GET https://markdownregistry.com/api/v1/blob/6587bf072243a87a39e1ac50c1433bb9b39a8e19b9deffd21b2f02495e484782
Your agent 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.