myco-settings SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
myco-settings from goondocks-co/myco is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add goondocks-co/myco/myco-settings@git:20261012.fe251e3Pins git:20261012.fe251e3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- goondocks-co/myco
- Path
packages/myco/skills/myco-settings/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261012.fe251e3, committed Oct 12, 2026
- First version recorded
- Sep 8, 2026
- Size
- 5,713 bytes
- Repository stars
- 14
- License
- Apache-2.0
Change a Myco deployment's settings safely, and add a new setting correctly. Deployment settings are one tier with one writer: every change admits the leaf, authorizes the actor, checks the leaf's own rule, persists it with its actor, and re-arms whatever schedule it moved — in that order, in one module. Bypassing that path is how one of those five steps quietly goes missing.
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
# Deployment settings
Myco 1.4 resolved settings across four tiers. 2.0 keeps two: what stays on the machine, and what the deployment holds. This skill is about the second.
## One writer, five steps, one order
Every write goes through the settings module, and it does five things in a fixed order:
1. **Admit the leaf** — is this a deployment-tier setting at all?
2. **Authorize the actor.**
3. **Check the leaf's own rule.**
4. **Persist it**, recording who changed it and when.
5. **Re-arm** any schedule the change moved.
The order is the point. Splitting these across call sites is how three of the four eventually go missing on one path and nobody notices. A gate holds every write to that one module, keyed on the tables themselves, so a second writer fails the build rather than drifting.
**Never write the settings table directly.** If you find yourself reaching for the database, you are adding the second writer the gate exists to prevent.
## A leaf carries its own rule, as data
A leaf's rule is declarative data, not a validator function. Three shapes exist:
| Shape | Means |
|---|---|
| `{}` | no rule; any JSON value |
…Read the whole file at its exact version.
How to install
mdr add goondocks-co/myco/myco-settings@sha256:24cdb3f7c2a6c0d3The line at the top of this page pins the label git:20261012.fe251e3, 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_qetppzgswgu3c7kb)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 8, 2026 and Oct 12, 2026, about one every 34 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.fe251e3 latest | 2026-10-12 | fe251e3 | 5,713 B | A | view · diff |
| git:20260908.a1143a2 | 2026-09-08 | a1143a2 | 5,418 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 (5713 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
goondocks-co/myco · 14 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qetppzgswgu3c7kb GET https://markdownregistry.com/api/v1/resolve?ref=goondocks-co/myco/myco-settings GET https://markdownregistry.com/api/v1/blob/24cdb3f7c2a6c0d380731fd6d613924840f8ce3b5fef93699d565f50f464fa0b
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 goondocks-co/myco
Every file in goondocks-co/myco