package-development skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
package-development is agent-read markdown (skill) from deathemperor/infinitus: Package registration. Use when adding a workspace package, making a private package publishable, renaming a package, or moving its workspace path..
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
Treat package work as a registration change, not a directory copy. ## Workflow 1. Inspect the closest package in the same family. Classify publication status, runtime, test environment, platform support, barrels, and dependency shape. Justify each proposed file by precedent or an explicit repository need. Continue when every proposed file is justified. 2. Create or move only required source, test, TypeScript, and manifest files. When manifest dependencies change, read [dependencies.md](dependencies.md) and classify every entry by role. Continue when pnpm discovers the intended name and manifests reference no absent file. 3. Read [registration.md](registration.md). Classify every registration surface as applicable or not applicable and update every applicable surface. Continue when every surface is classified and old references are explained. 4. For a published package, read [publishing.md](publishing.md) and verify its development and packed surfaces. 5. Run codegen when the package owns generated barrels, then inspect generated sections rather than editing them manually. …
Read the whole file at its exact version.
How to install
mdr add deathemperor/infinitus/package-development@git:20260918.e3c85eamdr add deathemperor/infinitus/package-development@sha256:0778f74bc4973d88Pin 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_ftr77tpq5562mljt)
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 (1959 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
deathemperor/infinitus · 6 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ftr77tpq5562mljt GET https://markdownregistry.com/api/v1/resolve?ref=deathemperor/infinitus/package-development GET https://markdownregistry.com/api/v1/blob/0778f74bc4973d88fc48fec480a2ddb8040e17747655fd2d031e69452d4d3c95
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.
More from deathemperor/infinitus
Every file in deathemperor/infinitus