init-verify SKILL.md skillA
init-verify from cryndoc/polisade-orchestrator is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cryndoc/polisade-orchestrator/init-verify@git:20261016.c36707dPins git:20261016.c36707d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cryndoc/polisade-orchestrator
- Path
skills/init-verify/SKILL.md- Versions recorded
- 9
- Latest version
- git:20261016.c36707d, committed Oct 16, 2026
- First version recorded
- Sep 7, 2026
- Size
- 14,482 bytes
- Repository stars
- 7
- License
- Apache-2.0
Verify that /polisade:init produced a canonical project structure (valid .state JSON, real polisadeVersion/schemaVersion, context file present) rather than content reconstructed from memory. Use when PM mentions "verify init", "check init", "validate project structure", "проверь init", "проверь инициализацию", or right after /polisade:init to confirm the generated files are byte-correct before reporting success.
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
# /polisade:init-verify — Verify Polisade Orchestrator init output
Guard-safe structural verification of a freshly initialized project. Reads
**only target-project files** (never the plugin install directory), so it runs
unblocked under the GigaCode Filesystem Guard. It exists to catch one failure
mode: a weak model that cannot Read the install dir silently
**reconstructs** state files from memory (e.g. `{"version": "5"}` instead of
`{"polisadeVersion": "...", "schemaVersion": 7}`, or an `.env.example` full of
`your_token_here`). Those reconstructions are structurally wrong and this check
makes them fail loud.
## Algorithm
1. Run the deterministic check below via `run_shell_command`. It reads only
files in the current project (`.state/*.json`, the context file,
`.env.example`) and prints exactly one `PASS` or `FAIL: <reason>` line.
```bash
${POLISADE_PYTHON:-python3} - <<'PY'
import hashlib, json, os, re, sys
# Bumped per release in lockstep with .claude-plugin/plugin.json. The
# match is enforced by polisade_lint_skills.py::check_version_consistency
# (version lockstep, 5th source) so this literal cannot silently drift.
…Read the whole file at its exact version.
How to install
mdr add cryndoc/polisade-orchestrator/init-verify@sha256:00a87d71558be618The line at the top of this page pins the label git:20261016.c36707d, 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_4du47s3nwy5yqru2)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 9 versions of this file, between Sep 7, 2026 and Oct 16, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.c36707d latest | 2026-10-16 | c36707d | 14,482 B | A | view · diff |
| git:20261012.4b1b6a8 | 2026-10-12 | 4b1b6a8 | 14,480 B | A | view · diff |
| git:20260915.af0e172 | 2026-09-15 | af0e172 | 14,170 B | A | view · diff |
| git:20260915.de884e2 | 2026-09-15 | de884e2 | 14,170 B | A | view · diff |
| git:20260911.1ea0673 | 2026-09-11 | 1ea0673 | 14,171 B | A | view · diff |
| git:20260910.6ccd621 | 2026-09-10 | 6ccd621 | 14,171 B | A | view · diff |
| git:20260909.15a67e6 | 2026-09-09 | 15a67e6 | 14,171 B | A | view · diff |
| git:20260908.af498fc | 2026-09-08 | af498fc | 13,556 B | A | view · diff |
| git:20260907.ad5db37 | 2026-09-07 | ad5db37 | 13,556 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 (14482 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
cryndoc/polisade-orchestrator · 7 stars · license Apache-2.0 · pushed 2026-10-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4du47s3nwy5yqru2 GET https://markdownregistry.com/api/v1/resolve?ref=cryndoc/polisade-orchestrator/init-verify GET https://markdownregistry.com/api/v1/blob/00a87d71558be61820f4df0c07b840a03022d802594b19d8a147ced93c5e2434
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.