Proposing okf-guard for community tools listing

Hi — I've built an open-source tool that complements the OKF ecosystem and wanted to check where community-built tools are tracked, and propose it for inclusion if there's a relevant list.

okf-guard is a content-safety scanning layer for OKF generation pipelines. It inspects raw source content (PDFs, Word docs, PowerPoint, spreadsheets, HTML) for hidden text and prompt-injection patterns before that content is written into an OKF concept file — complementing existing conformance validators (which check structural validity) with a check on content safety instead.

Targets the v0.2 schema — writes generated/sources fields, and deliberately never writes a verified field (since a tool asserting its own output as verified would defeat the purpose of that field per the spec).
Fully local and deterministic in this release — no network calls, no LLM dependency, single hard dependency (PyYAML).
Apache 2.0.

GitHub: https://github.com/darshanNhb/okf-guard
PyPI: pip install okf-guard

Happy to open a PR directly if there's a specific file this should go in (e.g., a community tools section in the README) — just let me know where that lives, or point me at the contributing guide if I've missed it.

Start with the repository README and contributing guide to find whether a community tools list already exists and where additions belong. Confirm the expected format with the issue thread, then add okf-guard and its GitHub or PyPI link to the appropriate listing. Done means the tool is documented in the agreed location without changing the schema or validator code.

Written by the indexing model from the issue text.