tech-specs-update SKILL.md skillA
tech-specs-update from cypher0n3/dotagents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cypher0n3/dotagents/tech-specs-update@git:20260910.9ed0c5cPins git:20260910.9ed0c5c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cypher0n3/dotagents
- Path
skills/tech-specs-update/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260910.9ed0c5c, committed Sep 10, 2026
- First version recorded
- Sep 9, 2026
- Size
- 1,938 bytes
- Repository stars
- 3
- License
- a license file GitHub does not identify
Update the related tech specs and requirements as part of planned work. Invoke only when explicitly called by user.
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
# Update Tech Specs Update the related tech specs and requirements as part of planned work, in the same change as the behavior they describe. A change that leaves a canonical document describing the old behavior is not complete. ## Identify What the Change Touches - Locate every requirement, technical specification, architecture document, and feature file that describes the behavior being changed. - Search by identifier, anchor, and domain term, not only by filename, because a single behavior is usually described in more than one place. - List what you found before editing, and say explicitly when a change touches no canonical document. ## Decide Before Editing - Confirm that the change is authorized to alter the specification, not just the code. Specs lead and code follows: if the implementation now contradicts an approved spec, that is a code gap to surface, not a document to quietly rewrite. - Stop and ask for direction when the change would weaken a requirement, alter an external contract, or resolve a contradiction between canonical documents. ## Apply the Update - Follow the repository's own authoring standards for the document being edited. …
Read the whole file at its exact version.
How to install
mdr add cypher0n3/dotagents/tech-specs-update@sha256:64d5ce21f7c179eaThe line at the top of this page pins the label git:20260910.9ed0c5c, 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_fudinvcedemvvyus)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 9, 2026 and Sep 10, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260910.9ed0c5c latest | 2026-09-10 | 9ed0c5c | 1,938 B | A | view · diff |
| git:20260909.eb38ca7 | 2026-09-09 | eb38ca7 | 1,893 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 (1938 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
cypher0n3/dotagents · 3 stars · license a license file GitHub does not identify · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fudinvcedemvvyus GET https://markdownregistry.com/api/v1/resolve?ref=cypher0n3/dotagents/tech-specs-update GET https://markdownregistry.com/api/v1/blob/64d5ce21f7c179eabcc95ad1e73ba65daa445e6393faaddef2b2bc0c8cbc53b0
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.