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 rules-validating-governancegit 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/rules-validating-governance)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/rules-validating-governance"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/rules-validating-governance/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/rules-validating-governance"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/rules-validating-governance.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.00069 | $0.00677 |
| Opus 5.5 | $0.00028 | $0.00271 |
| Sonnet 5.5 | $0.00014 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
rules-validating-governance 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validating Repository Governance Rules
Methodology for rules-checker, which validates repository-wide consistency across all
governance layers, agent/Skill duplication, and software-engineering documentation.
Reference Modules
- core-validation-and-agent-duplication.md and skills-duplication-and-report-formats.md — Core Repository Validation (naming, linking, emoji, No-Last-Updated), Agent-to-Agent Duplication, Agent-Skill Duplication, Skill-to-Skill Consolidation, Skills Coverage Gaps, and the finding report formats.
- word-budget-and-rules-governance-core.md and rules-governance-licensing-and-dependency-policy.md — governance word-budget delegation, contradictions/inaccuracies/inconsistencies, traceability, layer coherence, licensing compliance, dependency-bump policy compliance, Gherkin Gherkin journey coherence.
- software-docs-validation-8-1-to-8-4.md
and software-docs-validation-8-5-to-8-8.md —
the eight
docs/explanation/software-engineering/sub-checks (principle alignment, cross-references, naming, structure, templates, diagrams, README index, version docs). - preflight-consumption.md and
execution-sequence-and-report-structure.md —
consuming the deterministic
./rhino governance traceability validatepreflight JSON, the execution step sequence, and the final two-section report structure.
Core Principles
Deterministic boundary: in rules-quality-gate, every property the gate's Deterministic Boundary lists is
left to its declared tool. Retained layer-coherence and traceability checks remain domain findings.
Progressive writing: every finding is written immediately, never buffered — Step 8
(~265 files) is the step most likely to be interrupted by compaction. Conservative
consolidation: when uncertain whether Skills should merge, recommend KEEP SEPARATE.
What ships with it
10 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.
- README.md 538 B
- reference/core-validation-and-agent-duplication.md 4.2 KB
- reference/execution-sequence-and-report-structure.md 2.4 KB
- reference/preflight-consumption.md 2.3 KB
- reference/README.md 1.4 KB
- reference/rules-governance-licensing-and-dependency-policy.md 3.2 KB
- reference/skills-duplication-and-report-formats.md 3.9 KB
- reference/software-docs-validation-8-1-to-8-4.md 3.2 KB
- reference/software-docs-validation-8-5-to-8-8.md 3.1 KB
- reference/word-budget-and-rules-governance-core.md 3.7 KB
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 · 47 lines · 69 tokens per session scan A f9b94c2aabc8
rules-validating-governance is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 677 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
update-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
output-eval-error-analysis
Systematically review workflow traces to identify failure modes before building evaluators. Use when starting an eval project, after significant pipeline changes, or when production quality drops.
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…
pr-conflict-refresh
Find every open PR that is CONFLICTING/DIRTY against current main after a merge wave, ping its assigned dev to merge main into their branch and push, and track the re-test status.
react-frontend
React, TypeScript, and Next.js patterns for frontend development. Use when building React components, managing state, fetching data, optimizing performance, or working with Next.js App Router. Covers React 18-19, hooks, Server Components, and type-safe patterns.
iterative-converging-audit
Run any "find all instances of X" sweep — a security audit, a safety audit, a code review, a research question, a compliance check — as an iterative loop that does NOT stop at one pass. Audit → fix → RE-audit → … until a clean pass returns zero NEW discoveries. Use whenever thoroughness matters and a single pass would…