sttp-enforce SKILL.md skillA
sttp-enforce from frolad/tars is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add frolad/tars/sttp-enforce@git:20261104.96c9a51Pins git:20261104.96c9a51 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- frolad/tars
- Path
skills/sttp-enforce/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261104.96c9a51, committed Nov 4, 2026
- Size
- 5,266 bytes
- Repository stars
- 3
- License
- MIT
Bring the files under a path to sttp's rules. The first turn analyses the files and lists what sttp would change, by kind (prose, repetition, headings, tables, code comments, contradictions), each item numbered with a recommendation; the files are written after the user picks.
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
sttp and sttp-software-engineering apply. `/sttp-enforce <path>` (`$sttp-enforce` in Codex) brings the text of the files under a path, a file, a folder or a package, to sttp's rules. What sttp says of an answer holds for a file: the point first, only the subject, every fact kept, nothing the reader can do without. The first turn is the analysis; the files are written after the user picks what to change. ## The files - The path is a file, or a folder with every file under it that git does not ignore. With no path, ask for one. - Left out, and named in one line in the analysis: generated files, vendored code, lock files, binaries, licenses and other legal text, and text whose form is set elsewhere, such as test fixtures and data a test reads, or a changelog in a fixed format. - A file with changes that are not staged is named in the analysis: `git diff` would show them mixed with this run's. - Outside a git repository there is no diff to review: suggest a folder for copies of the old files, and ask. - More files than one turn can read in full: say how many, suggest going folder by folder, and ask. ## The analysis: the first turn …
Read the whole file at its exact version.
How to install
mdr add frolad/tars/sttp-enforce@sha256:d5c7d7591e360741The line at the top of this page pins the label git:20261104.96c9a51, 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_o6ca5fie7krynjzo)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 4, 2026.
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 (5266 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
frolad/tars · 3 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o6ca5fie7krynjzo GET https://markdownregistry.com/api/v1/resolve?ref=frolad/tars/sttp-enforce GET https://markdownregistry.com/api/v1/blob/d5c7d7591e360741bcd0a86fddfc98843fcc43c5b899e596f10ed00d71f70971
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.