Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add wahidyankf/ose-public --skill specs-validating-structuregit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/wahidyankf/ose-public/specs-validating-structure)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/specs-validating-structure"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/specs-validating-structure/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wahidyankf/ose-public/specs-validating-structure"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/specs-validating-structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00070 | $0.00702 |
| Opus 5.5 | $0.00028 | $0.00281 |
| Sonnet 5.5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
specs-validating-structure scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validating Specs Structure
Methodology for validating explicitly-listed specs/ folders (and their subfolders) for
structural completeness, content accuracy, internal consistency, and cross-folder coherence.
Scope Rule
Validate only explicitly listed folders and their subfolders — never implicit discovery. Cross-folder consistency (Category 4) runs only when 2+ folders are listed; it's skipped for a single folder. Subfolders are always included automatically.
Lifecycle Delegation
Under a quality gate, do not re-derive, report, or fix a property the gate's Deterministic Boundary lists, per the
Quality Gate Contract. The gate md-internal-link (pre-commit and pull-request) owns missing link targets: outside a quality gate,
run ./rhino md internal-link validate for them, and check #fragment anchors yourself, because it does not. Keep Gherkin journey coherence,
semantic, and cross-folder judgment.
The Nine Validation Categories
See reference/validation-categories-1-4.md for Structural Completeness (README coverage), Feature File Inventory Accuracy, Gherkin Format Compliance, and Cross-Folder Consistency, and reference/validation-categories-5-9.md for C4 Diagram Consistency, Cross-Reference Integrity, Spec-to-Implementation Alignment, Spec Tree Shape Compliance and Adoption Gaps (review-owned: no deterministic check exists).
Drift Detection, Execution Pattern, and Report Format
See reference/drift-detection-and-reporting.md for current deterministic commands, lifecycle filtering, the six-step execution pattern, and the full audit report template.
Fixer Mechanics
See reference/fixer-disposition.md for how specs-fixer
maps each of the nine categories to a fix disposition (auto-fixable / requires review / skip), and
reference/fixer-execution-and-safety.md for its
execution pattern, fix report format, safety rules, and changed-file capture.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 58 lines · 70 tokens per session scan A e132e415de8e
specs-validating-structure is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 702 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-14.
Other skills, from other repositories
pptx-html-fidelity-audit
Audit a python-pptx export against its source HTML deck, identify layout/content drift (footer overflow, cropped content, missing italic/em, lost styling, off-rhythm spacing), and re-export with strict footer-rail + cursor-flow layout discipline. Use this skill whenever the user has a .pptx that was generated from an…
ux-acceptance-coordinator
Coordinate black-box, agent-driven UX acceptance journeys against a disposable EmDash admin site. Use when preparing, dispatching, verifying, or reporting a manual browser journey performed by a separate tester agent. Do not use for deterministic Playwright tests or ordinary code review.
ux-acceptance-tester
Perform a goal-driven, black-box UX acceptance journey in a browser and report the path, friction, and observable outcome. Use only in an isolated tester context with a supplied start URL and brief.
define-data
Standalone Phase 4 of SAP UI testing. Authors one tests/ /test-cases/TC-XXX.data.md requirement spec per case marked dataRequired: yes — choosing the narrowest correct source (sql/static/generated/seeded), and generating upload fixtures in the EXACT file format the program parses (xlsx vs csv). Validates that every…
puppeteer-skill
Generates Puppeteer scripts for browser automation, scraping, and PDF generation. Triggers on: "Puppeteer", "headless Chrome", "page.goto", "scrape", "PDF generation".
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…