rule-proposer SKILL.md skillA
rule-proposer from ymd38/dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ymd38/dev-skills/rule-proposer@git:20261022.fe6cd68Pins git:20261022.fe6cd68 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ymd38/dev-skills
- Path
skills/rule-proposer/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261022.fe6cd68, committed Oct 22, 2026
- Size
- 8,343 bytes
- Repository stars
- 7
- License
- MIT
Turn security findings into Semgrep rules. Reads vulnerability-scan reports, confirmed sakuda findings (via its MCP, when configured) and manual-review notes; decides per candidate whether it can be a rule at all; drafts the rule and its `semgrep --test` fixture in a scratch directory; measures hits and false positives across the repository; and writes approved rules to `.semgrep/rules/`. Rules that do not depend on the application's own names are offered as a pull-request draft for maruda's…
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
# Role: Semgrep Rule Author (Proposal-First) A finding fixed once can come back with the next change. A rule makes the scanner catch it every time. Your job is to turn findings into rules **where a rule can honestly catch them**, and to say plainly where it cannot. Every rule you propose has been run: its fixture passes `semgrep --test`, and you know how many places it hits in this repository and how many of those are false positives. **Nothing is written to the repository before the user approves.** Drafts live in a scratch directory. After approval, the only place you write is `.semgrep/rules/`. ## Inputs Collect whichever exist; ask which to use when there are several. | Source | Where | What to take | |--------|-------|--------------| | vulnerability-scan report | `docs/security-audit/*.md` (not `rule-proposals.*`) | True Positives (`### V-XX`) with their `file:line` and vulnerable code | | sakuda confirmed findings | sakuda MCP: `list_sites` → `list_scans` → `list_findings` | Findings whose triage is `confirmed`; or a `sakuda-triage` report in `docs/security-audit/` | | Manual-review notes | a file or text the user points to | The flaw, and the code location if known | …
Read the whole file at its exact version.
How to install
mdr add ymd38/dev-skills/rule-proposer@sha256:ff3ae7bc06dbb2f7The line at the top of this page pins the label git:20261022.fe6cd68, 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_qphzcvkn47cgynct)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 22, 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 (8343 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
ymd38/dev-skills · 7 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qphzcvkn47cgynct GET https://markdownregistry.com/api/v1/resolve?ref=ymd38/dev-skills/rule-proposer GET https://markdownregistry.com/api/v1/blob/ff3ae7bc06dbb2f793fef7cc45b85f914f2f94654d17d660f0fe2347cecc93a8
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 ymd38/dev-skills
Every file in ymd38/dev-skills